菜单
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".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/doodledood/claude-code-plugins --skill address-pr-comments命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | address-pr-comments |
| description | 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.
Classify all unresolved PR comments against false positive criteria, report triage findings, then fix actionable items with user confirmation per fix.
| 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:
false-positiveactionableuncertain (report, don't fix)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:
Completion summary: After all items processed, summarize actions taken (fixes applied, false positives skipped, uncertain items flagged).
| 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" |
End-to-end autonomous execution: figure-out → define → do, chained without manual approval gates. Use when you want to define and execute without intervention during planning, when the user asks for autonomous or end-to-end work, says just build it, or asks to tend or babysit a PR.
Author-side PR lifecycle babysitter and companion to review-pr. Use when the user wants to tend an existing GitHub PR through CI, review threads, description sync, mergeability, auto-fixes, or asks to babysit a PR with or without an existing manifest.
Manifest executor. Works through Deliverables verifying every Acceptance Criterion and Global Invariant. Use when executing a manifest, running a plan, implementing a defined task, or when the user asks to run, execute, implement, or ship a manifest-backed plan.