What problem does it solve?
This Skill helps you navigate code review feedback by ensuring technical rigor and verification before implementation, preventing performative agreement or blind execution of potentially flawed suggestions.
Core Features & Use Cases
- Structured Response Pattern: Follows a clear process: Read, Understand, Verify, Evaluate, Respond, Implement.
- Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
- External Reviewer Scrutiny: Outlines a verification checklist for feedback from sources outside your immediate team.
- YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary feature creep.
- Use Case: When a reviewer suggests a change that seems technically unsound or unnecessary for the current project goals, this Skill guides you to ask clarifying questions, push back with technical reasoning, or verify its necessity against actual codebase usage.
Quick Start
When receiving code review feedback, verify its technical soundness against the codebase before implementing any suggestions.