review-address-comments
Skill1 starsChanged 5 months agoMITView on GitHub
Use when review comments, requested changes, or PR feedback must be processed systematically. This skill groups comments, decides what to accept, and turns feedback into verified edits instead of ad hoc reactions.
In this repository21 other files it gives its agents.
- api-contract-compatibility-reviewSkill
- architecture-refactor-guidanceSkill
- browser-verificationSkill
- change-impact-analysisSkill
- cost-impact-reviewSkill
- data-migration-safety-reviewSkill
- data-quality-auditSkill
- dependency-compliance-auditSkill
- docs-writerSkill
- environment-config-auditSkill
- fix-ciSkill
- incident-observability-triageSkill
- performance-investigationSkill
- planningSkill
- release-incident-postmortemSkill
- release-rollout-strategySkill
- security-reviewSkill
- ship-readinessSkill
- dev-workflow-kitSkill
- systematic-debuggingSkill
- test-strategy-gap-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when collaboration after implementation becomes the main task.
- Distinctive: line 13
Use this skill when:
- Distinctive: line 20
Do not use this skill for initial implementation planning or for pure status lookups without feedback to process.
- Distinctive: line 28
Verify each changed area.
- Very specific: line 44
use fix-ci if review-triggered changes break automation
- Very specific: line 45
use ship-readiness before final merge
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Address Comments
Use this skill when collaboration after implementation becomes the main task.
Trigger Conditions
Use this skill when:
- a PR has reviewer comments
- the user asks to address requested changes
- feedback needs to be grouped or prioritized
- multiple comment threads refer to overlapping concerns
- the branch needs a clear resolution summary after edits
Do not use this skill for initial implementation planning or for pure status lookups without feedback to process.
Workflow
- Gather the comments and group them by theme.
- Distinguish must-fix issues from optional suggestions.
- Identify overlapping comments and consolidate the work.
- Apply the smallest changes that resolve accepted feedback.
- Verify each changed area.
- Summarize what was addressed and any intentional non-changes.
Output
For non-trivial work, provide:
- grouped feedback themes
- accepted vs deferred items
- edit plan
- verification evidence
- resolution summary
Coordination
After comment processing:
- hand off to the active coding workflow for implementation edits
- use
fix-ciif review-triggered changes break automation - use
ship-readinessbefore final merge
Invocation Examples
- "Use review-address-comments to classify and resolve this PR feedback."
- "Use review-address-comments and turn these requested changes into an action list."
- "Use review-address-comments after the last review round and summarize what remains."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.