pull-request

Opens GitHub pull requests from feature branches and collects review feedback as structured task entries.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill pull-request-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/pull-request
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill pull-request-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating pull request creation, local test verification, and review feedback collection across feature branches is repetitive and error-prone in multi-agent development workflows. This Skill automates the full PR lifecycle: enforcing a local test gate before pushing, opening the PR with gh CLI, and classifying reviewer comments and CI failures into structured, actionable task entries for a coordinator agent. ## Core Features & Use Cases - Mandatory Local Test Gate: Runs the configured test suite and build before any push or PR creation, blocking the workflow and reporting failures if tests do not pass. - Automated PR Creation: Opens pull requests with gh pr create using the correct base branch read from task files, with structured titles and bodies covering implementation summary, architecture decisions, and test coverage. - Structured Feedback Collection: Waits for CI and review activity, then classifies every comment as needs-code-change, ci-failure, question, or acknowledged in a standardized PR Feedback section. - Use Case: In a multi-agent coding workflow, after a coder agent finishes a feature branch, dispatch this agent to verify tests pass, open the PR against the correct base branch, and return a classified list of review comments so the coordinator can dispatch follow-up fix tasks. ## Quick Start Ask the agent to open a pull request for the current feature branch, run the local test gate first, and return the classified review feedback.

Frequently Asked Questions about pull-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation with the GitHub CLI?▼

Use gh pr create with --base and --head flags to open a PR from a feature branch. This Skill reads the base branch from a task file, builds a structured title and body, and runs the command after a mandatory local test gate passes.

How to collect and classify GitHub PR review comments automatically?▼

Fetch comments with gh pr view --json number,url,comments,reviews,statusCheckRollup, then classify each item as needs-code-change, ci-failure, question, or acknowledged. The result is written as a structured PR Feedback section for a coordinator to act on.

Can I push a branch and open a PR if local tests are failing?▼

No. The local test gate is a hard requirement: if the configured test suite or build fails, the agent stops, writes a failure report, and returns control without pushing or opening a PR. Only platform-missing-tool errors qualify for a documented skip.

Does this workflow support GitHub Projects board integration?▼

Yes. When workflow.backend is set to github_project in agent.yaml, PR feedback is also forwarded to a board-man agent as issue comments, and tasks are marked DONE on the project board once all comments are resolved and the merge lands.

What happens when a PR review comment is ambiguous?▼

Ambiguous comments default to needs-code-change so the coordinator can decide whether to dispatch a fix task. The agent never modifies code itself; it only collects and classifies feedback.