What problem does it solve?
This Skill addresses the common issue of blindly implementing code review feedback without proper technical verification, which can lead to wasted effort, regressions, or the introduction of incorrect changes. It promotes a rigorous, verification-first approach to code review responses.
Core Features & Use Cases
- Structured Response Pattern: Guides users through a clear, step-by-step process for handling feedback (Read, Understand, Verify, Evaluate, Respond, Implement).
- Technical Verification: Emphasizes checking feedback against the codebase's reality and technical constraints before implementation.
- Reasoned Pushback: Provides guidance on how and when to push back against feedback with technical reasoning.
- Handling External Feedback: Specific protocols for evaluating suggestions from external reviewers versus internal team members.
- Use Case: When a reviewer suggests a change, instead of immediately agreeing and implementing, this Skill prompts you to first verify if the suggestion is technically sound for the current codebase, doesn't break existing functionality, and aligns with project goals (YAGNI).
Quick Start
When receiving code review feedback, follow the structured response pattern to verify and evaluate each item before implementing.