review-response
Installation
SKILL.md
Review Response
Purpose
Turn review feedback into verified, correctly-scoped changes. Technical correctness outranks social comfort: no performative agreement, no blind implementation, no gratitude phrases — actions and technical reasoning carry the response.
Workflow
- Read the complete feedback without reacting. Do not start implementing mid-read.
- Restate each item as a technical requirement in your own words. If any item is unclear, stop and ask about it before implementing anything — items may be related, and partial understanding produces wrong implementations.
- Verify each item against codebase reality: is it technically correct for this codebase, does it break existing behavior, is there a reason the code is as it is, does it hold across supported platforms and versions?
- Evaluate scope: if a suggestion proposes "proper" infrastructure, check actual usage first — unused endpoints and unrequested features are YAGNI candidates to raise, not build.
- Respond per item: implement what is correct, answer questions directly, ask about what is unclear, push back with technical reasoning on what is wrong.
- Implement accepted items one at a time, in order: blocking issues (breaks, security) first, then simple fixes, then complex refactoring. Run an individual test for each fix and check for regressions only when the user explicitly authorizes that covered operation; otherwise apply the fix, record that tests were not run because authorization is missing, and hand off the completion claim to
verification-before-completion. - When replying to inline review threads on a forge, reply inside the comment thread, not as a new top-level comment.