What problem does it solve?
This Skill addresses the challenge of receiving code review feedback by ensuring that suggestions are technically sound, relevant to the codebase, and understood before implementation, preventing the adoption of incorrect or unnecessary changes.
Core Features & Use Cases
- Structured Response Pattern: Guides the user through a systematic process of reading, understanding, verifying, evaluating, responding, and implementing feedback.
- Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback to avoid misinterpretations.
- External Reviewer Scrutiny: Implements a rigorous check for external suggestions, ensuring technical correctness, impact on existing functionality, and alignment with project context.
- YAGNI Enforcement: Includes a check to remove unused features suggested by reviewers, adhering to the "You Ain't Gonna Need It" principle.
- Use Case: When a reviewer suggests a change that seems technically off or unnecessary, this Skill prompts a verification process, potentially leading to a reasoned pushback or a targeted clarification, rather than blind acceptance.
Quick Start
When receiving code review feedback, first read and understand the feedback completely, then verify its technical soundness against the codebase before responding or implementing.
