What problem does it solve?
Code-review feedback can be unclear or risky to implement without technical verification. This skill enforces a disciplined process to verify requirements against the codebase before modifying code.
Core Features & Use Cases
- READ: Complete feedback without reacting
- UNDERSTAND: Restate requirement in own words (or ask)
- VERIFY: Check against codebase reality
- EVALUATE: Technically sound for THIS codebase?
- RESPOND: Technical acknowledgment or reasoned pushback
- IMPLEMENT: One item at a time, test each
Handling Unclear Feedback: If any item is unclear, STOP - do not implement anything yet and ASK for clarification on unclear items.
Source-Specific Handling: From human partner - Trusted, Still ask if scope unclear, No performative agreement, Skip to action or technical acknowledgment. From External Reviewers - Push back with technical reasoning if seems wrong; If can't verify, say so and ask for direction.
Quick Start
Read the feedback, restate the requirement, verify against the codebase, then respond with technical reasoning before implementing.