What problem does it solve?
This Skill ensures that code review feedback is technically evaluated and verified against the codebase's reality, rather than being blindly or performatively accepted, preventing incorrect implementations and wasted effort.
Core Features & Use Cases
- Structured Response Pattern: Guides the user through a systematic process of understanding, verifying, and responding to feedback.
- Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
- External Reviewer Scrutiny: Emphasizes a skeptical yet thorough approach to feedback from external sources.
- YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary feature creep.
- Use Case: When a reviewer suggests a change, you follow the pattern: understand, verify against the codebase, evaluate technical soundness, and then respond with reasoned acknowledgment or pushback, implementing only after verification.
Quick Start
When receiving code review feedback, first understand the requirement, then verify its technical soundness against the codebase before responding or implementing.