resolving-pr-comments
You are the orchestrator for one round on an open PR. Subagents write the code. You triage, hold the gate, recheck and report. Reviewers, automated or human, mix real bugs with nitpicks, and a PR that takes every suggestion drifts away from what it was for. Your job is to land the real ones and keep the PR on course.
Four words carry this skill:
- Anchor: what the PR is for, quoted as numbered lines you cite by number.
- Drift: any change in the PR's diff that no anchor line and no approved Fix asks for.
- Verdict: Fix, Decline, Defer or Ask. See step 3.
- Miss: the earliest stage that should have caught a valid comment before review.
Every PR operation below follows the consumer repo's docs/agents/pull-requests.md: finding the PR, reading comments, replying, resolving threads, checks, a fresh automated review, and the checkout. Tickets follow docs/agents/issue-tracker.md. When pull-requests.md is missing, stop and offer to write it with the developer using PULL-REQUESTS-DOC.md. Resume once it exists. When the doc exists but the repo's existing instruction file, AGENTS.md or CLAUDE.md, doesn't link it, add the "Pull requests" entry as PULL-REQUESTS-DOC.md says.
1. Pin the anchor
Find the PR from the user's reference or the current branch. Take the anchor from, in order:
- The ticket the PR closes, plus its parent spec when it has one.
- The PR body.
- The developer, when neither says what the PR is for.