Resolving PR Review Comments

Use only after explicit invocation. Treat comments as claims to verify, not instructions to apply blindly. Invocation authorizes inspection, bounded local fixes, checks, and focused local commits; it does not by itself authorize public replies, thread resolution, or a push.

Establish Scope

1. Inspect git status --short --branch, git diff --cached --name-only, and the symbolic branch. Stop before editing if the index already contains changes; preserve unrelated unstaged/untracked work and stop on overlap.
2. Resolve the PR's repository, number, URL, state, base, head repository, head branch, and cross-repository status from the provider. Confirm attached HEAD is the PR head and compare against the reported base merge point; never assume main.
3. Collect every paginated feedback surface: top-level comments, submitted reviews, inline comments, and thread state including IDs, outdated status, and resolution. An empty summary is not proof that no feedback exists.

Assess and Fix

Classify each substantive comment:

• Reasonable and unresolved: evidence confirms a contract or behavior defect; fix it.
• Already addressed/outdated: current code resolves it; cite file, commit, or test evidence.
• Not reasonable: premise conflicts with requirements or adds unjustified scope; prepare a concise evidence-based response.
• Ambiguous/disputed: a behavior decision or external fact is missing; ask one focused question or leave it open.