How do I install the Address Pr Comments skill?

Run npx skillmds@latest add doodledood/address-pr-comments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Address Pr Comments safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Address Pr Comments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Address Pr Comments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Address Pr Comments?

doodledood (@doodledood) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Address Pr Comments by doodledood — Agent Skill

Name: Address Pr Comments
Rating: 4.2 (5 reviews)
Author: doodledood

Address Pr Comments

Triage and fix PR review comments. Reads comments, filters false positives (outdated, misread, wrong context, style preference), validates relevance against current diff, and fixes valid ones with confirmation. Use when: "fix pr comments", "address review feedback", "handle pr feedback".

doodledood 5cca08a 2.5 KB Updated Sep 10, 2026

File contents

User request: $ARGUMENTS

If no PR specified: Detect PR from current branch. If detection fails, report and stop.

Default scope: All unresolved comments on the PR.

Goal

Classify all unresolved PR comments against false positive criteria, report triage findings, then fix actionable items with user confirmation per fix.

False Positive Detection

Type	Detection Signal
Outdated	Suggested change already exists in code; commit history shows it was addressed
Misread code	Comment's premise contradicts what code actually does
Wrong context	Comment references behavior/variables not present in the target code
Style preference	No functional or readability improvement—evaluate substance, not reviewer's tone. Naming changes that aid comprehension are actionable, not style preference
Resolved in thread	Reply discussion shows issue was already addressed or withdrawn

Classification:

Strong false-positive signal → false-positive
Real issue with clear fix → actionable
Unclear validity → uncertain (report, don't fix)

Output

Triage report: Classification, reasoning, and summary counts for each comment. Format flexibly based on volume.

Per-fix flow: For each actionable item, show original comment and proposed change, then ask user to confirm with these options:

Fix + resolve thread (recommended) — apply fix, resolve the PR comment thread
Fix only — apply fix, leave thread unresolved
Skip — don't apply this fix

Completion summary: After all items processed, summarize actions taken (fixes applied, false positives skipped, uncertain items flagged).

Constraints

Constraint	Enforcement
Verify before classifying	Read actual code and reply threads; never classify from comment text alone
Conservative on fixes	Uncertain → report only
Explain rejections	Every false-positive needs reasoning
Per-fix confirmation	User confirms each fix individually
Resolve only when chosen	Only resolve threads or reply to comments when user selects "Fix + resolve"

---name: address-pr-commentsdescription: Triage and fix PR review comments. Reads comments, filters false positives (outdated, misread, wrong context, style preference), validates relevance against current diff, and fixes valid ones with confirmation. Use when: "fix pr comments", "address review feedback", "handle pr feedback".---**User request**: $ARGUMENTS**If no PR specified**: Detect PR from current branch. If detection fails, report and stop.**Default scope**: All unresolved comments on the PR.## GoalClassify all unresolved PR comments against false positive criteria, report triage findings, then fix actionable items with user confirmation per fix.## False Positive Detection| Type | Detection Signal ||------|------------------|| **Outdated** | Suggested change already exists in code; commit history shows it was addressed || **Misread code** | Comment's premise contradicts what code actually does || **Wrong context** | Comment references behavior/variables not present in the target code || **Style preference** | No functional or readability improvement—evaluate substance, not reviewer's tone. Naming changes that aid comprehension are actionable, not style preference || **Resolved in thread** | Reply discussion shows issue was already addressed or withdrawn |**Classification**:- Strong false-positive signal → `false-positive`- Real issue with clear fix → `actionable`- Unclear validity → `uncertain` (report, don't fix)## Output**Triage report**: Classification, reasoning, and summary counts for each comment. Format flexibly based on volume.**Per-fix flow**: For each actionable item, show original comment and proposed change, then ask user to confirm with these options:1. **Fix + resolve thread** (recommended) — apply fix, resolve the PR comment thread2. **Fix only** — apply fix, leave thread unresolved3. **Skip** — don't apply this fix**Completion summary**: After all items processed, summarize actions taken (fixes applied, false positives skipped, uncertain items flagged).## Constraints| Constraint | Enforcement ||------------|-------------|| Verify before classifying | Read actual code and reply threads; never classify from comment text alone || Conservative on fixes | Uncertain → report only || Explain rejections | Every false-positive needs reasoning || Per-fix confirmation | User confirms each fix individually || Resolve only when chosen | Only resolve threads or reply to comments when user selects "Fix + resolve" |

Frequently asked questions