What problem does it solve?
Code-review feedback can be unclear or technically questionable. This skill provides a disciplined, verifiable approach to interpret feedback, verify it against the codebase, and apply changes incrementally to ensure correctness.
Core Features & Use Cases
- Structured response pattern: Read, understand, verify, evaluate, respond, and implement in a controlled sequence to prevent rash changes.
- Clarification when unclear: If any item is ambiguous, stop and request clarification before proceeding.
- Source-specific handling: Differentiate between trusted human partners and external reviewers, with appropriate pushback when scope is unclear.
- YAGNI and validation checks: Assess whether suggested changes are actually needed and verify their impact before applying.
- Implementation discipline: Prioritize blocking issues, then simple fixes, then complex refactors; test each change individually to avoid regressions.
- Communication style: Provide technical acknowledgment or reasoned pushback without performative agreement.
Quick Start
When you receive code-review feedback, read it carefully, clarify unclear items, verify against the codebase, and implement changes one item at a time after validation.