address-review

Triage and resolve inbound GitHub PR review comments with batched fixes and replies.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill address-review-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-review
Source: https://github.com/pnewsam/skills/tree/main/archive/registry-rebuild/address-review
Command: npx skills add https://github.com/pnewsam/skills --skill address-review-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling reviewer feedback on a GitHub pull request is error-prone: pushing new commits can dismiss an existing approval, threads get silently dropped, and replies go out before fixes land. This Skill triages every unresolved review thread, decides whether to fix, reply, defer, or fold it into another PR, and executes each step only with explicit authorization. ## Core Features & Use Cases - Thread triage: Fetches review threads via the GitHub CLI and GraphQL API, classifies each as must-fix, nit, question, out-of-scope, or stale, and proposes a disposition table. - Staged execution modes: Triage, Address, Respond, and Publish modes gate local commits, thread replies, resolutions, and pushes as separately authorized steps. - Approval protection: Checks approval state before pushing, batches accepted changes so an approval is invalidated at most once, and files follow-up issues for deferred items. - Use Case: A reviewer left twelve comments on your approved PR. Run the skill to classify each comment, implement the accepted fixes as grouped commits, reply with rationales, resolve addressed threads, and confirm before the single push that dismisses the stale approval. ## Quick Start Use the address-review skill to triage the review comments on this PR and propose how to address each one.

Frequently Asked Questions about address-review

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

FAQPage Schema
How do I address review comments on a GitHub pull request?▼

Fetch unresolved review threads with the GitHub CLI, classify each as must-fix, nit, question, or out-of-scope, then implement accepted fixes as grouped commits. Reply to each thread with a one-line rationale and resolve only the threads you actually addressed.

How do I reply to and resolve PR review threads with the GitHub CLI?▼

Reply with gh api repos/<owner>/<repo>/pulls/<n>/comments passing the body and in_reply_to comment ID. Resolve the thread with the resolveReviewThread GraphQL mutation using the thread ID, then verify the resolution state.

Does pushing new commits dismiss an existing PR approval?▼

Yes, on repositories configured to dismiss stale approvals, any new push invalidates the approval. This skill checks approval state first, batches all accepted changes into one push, and always asks for confirmation before pushing.

What should I do with out-of-scope review comments?▼

Reply to the thread explaining the deferral, open a follow-up issue, and link it in the reply instead of resolving silently. Non-urgent nits can also be folded into another in-flight PR that already touches the same file.

When should I not resolve a review thread?▼

Never resolve a thread you have not actually addressed with a committed change or a clear replied decision. Every thread must end as fixed, replied-with-rationale, deferred-to-follow-up, or folded-into-another-PR, with the disposition visible to the user.