What problem does it solve?
This Skill addresses the challenge of receiving code review feedback by ensuring that suggestions are technically sound, understood, and verified against the codebase before implementation, preventing unnecessary work and potential regressions.
Core Features & Use Cases
- Structured Response Pattern: Provides a clear, step-by-step process for handling feedback (Read, Understand, Verify, Evaluate, Respond, Implement).
- Handling Ambiguity: Guides users on how to seek clarification for unclear feedback to avoid misinterpretation.
- External Reviewer Scrutiny: Implements a rigorous check for external suggestions, ensuring technical correctness and context awareness.
- YAGNI Principle Enforcement: Helps in questioning the necessity of new features suggested during reviews if they are not currently used.
- Graceful Pushback: Offers strategies for respectfully disagreeing with feedback when technically justified.
- Use Case: When a reviewer suggests a change, you first verify its technical merit and impact on the existing codebase, ask clarifying questions if needed, and only then proceed with implementation, documenting the verified change.
Quick Start
When receiving code review feedback, verify each item against the codebase and ask for clarification on anything unclear before implementing.