with one click
address-pr-feedback
// Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply.
// Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply.
Make one focused code change: understand the task, make the smallest complete change, test it, verify it, and report.
Review a code change for correctness, security, broken contracts, robustness, and real tests.
Write a lightweight technical design document for ambiguous or consequential architecture decisions before implementation.
Improve the shape of existing code without changing behavior.
Write an implementation spec to docs/<feature-slug>/spec.md and pause for human review. Use when the user says "write a spec", "spec this out", "technical design", "design doc", or when a task has decisions, invariants, or contracts that should be reviewed before code is written.
Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.
| name | address-pr-feedback |
| description | Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply. |
| user-invocable | true |
| argument-hint | <PR URL, PR number, branch, or optional focus> |
Use this after a pull request has review comments. Review feedback is input, not instruction: judge each comment against the current code, then fix the valid issues.
$ARGUMENTS.gh, starting with:
gh pr view --json number,url,title,body,baseRefName,headRefName,reviewDecision,statusCheckRollupgh pr diffgh api graphql for reviewThreads if flat comments lose thread context.For each thread or comment, inspect the current code around the referenced file and line. Classify it as:
Group related comments by underlying issue. Do not implement comments just because they exist.
browser-verify when available.Draft a concise reply for each thread or comment using one of these statuses:
Post replies, resolve threads, push commits, or mark checks complete only when the user explicitly asks. If posting replies, keep them short and factual.
Summarize:
Fixed unless the code changed or was already correct and verification supports the claim.