Agent skill · Code Review & Quality

review-comments-resolver

Resolve a document's forty review comments systematically — triage by type (accept, push back, conflict, out-of-scope), batch the mechanical fixes, draft the disagreement replies, and reconcile reviewers who contradict each other. Use when asked work through these review comments, two reviewers want opposite things, close out the feedback on this doc, or which comments do I actually have to take. Produces the comment triage, the batched fixes, the push-back replies, the conflict reconciliations, and the closure sweep.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill review-comments-resolver --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/review-comments-resolver/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Review Comments Resolver Skill A document with forty comments induces either capitulation (accept-all, the doc becomes committee mush) or avoidance (the comments age until the doc ships around them). Resolution is triage: most comments are mechanical (accept in batch, thank in aggregate), some are substantive-and-right (accept with the change named), some deserve push-back (drafted politely, decided by the doc's owner), and a few *contradict each other* — those aren't the author's to split; they get reconciled by naming the conflict to its parties. Every comment ends closed, and the doc stays the author's. ## What This Skill Produces - **The triage table** — every comment sorted: accept-mechanical / accept-substantive / push-back / conflict / out-of-scope - **The batch plan** — mechanical fixes applied in one pass, resolved with one courtesy note - **The push-back replies** — drafted: the reviewer's point honored, the decision explained, the owner's call made - **The conflict reconciliations** — contradicting reviewers named to each other with the author's recommendation - **The closure sweep** — nothing left dangling; the resolved-vs-declined summary if the doc's approver wants

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Resolution Rules
  4. Output Format
  5. The Triage
  6. Batch Pass
  7. Push-Backs (drafted)
  8. Conflicts (reconciled)
  9. The Sweep
  10. Quality Checks
  11. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the review-comments-resolver skill do?

Resolve a document's forty review comments systematically — triage by type (accept, push back, conflict, out-of-scope), batch the mechanical fixes, draft the disagreement replies, and reconcile reviewers who contradict each other. Use when asked work through these review comments, two reviewers want opposite things, close out the feedback on this doc, or which comments do I actually have to take. Produces the comment triage, the batched fixes, the push-back replies, the conflict reconciliations, and the closure sweep.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill review-comments-resolver --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going