| name | handle-pr |
| description | Review an incoming PR end-to-end — strict local review, drafted GitHub review, post after confirmation |
| argument-hint | <pr-number> |
| allowed-tools | Task, Bash, Read, Glob, Grep, Write, mcp__github__get_pull_request, mcp__github__get_pull_request_files, mcp__github__create_pull_request_review |
Handle PR
Review an incoming pull request end-to-end: a strict local review against
REVIEW_CRITERIA.md (including scope and spec satisfaction), distilled into a
GitHub review draft, posted only after user confirmation. Internal and
external PRs are treated the same.
For later rounds — after the author responds to a posted review — use
/follow-up-review <number> instead (it is round-aware: it verifies the prior
requested changes against the delta and reads the author's replies).
/address-review is the author-side counterpart, for feedback on a PR you
authored — not for re-reviewing an incoming PR.
Arguments
/handle-pr <pr-number>
Workflow
Step 1: Pre-Checks
Fetch the PR (mcp__github__get_pull_request). Check before any deep
review:
- Scope: does the PR address exactly one concern (CONTRIBUTING.md: one
PR, one concern)? If it clearly bundles unrelated changes, the review can
short-circuit: the primary finding is "split this PR", detailed findings
are secondary
- Linked spec/issue: identify the linked issue from the PR body or
branch name. If it links a issue, that spec is the verification
target