What problem does it solve?
This Skill helps you navigate code review feedback by ensuring technical rigor and verification before implementation, preventing performative agreement and blind execution of potentially flawed suggestions.
Core Features & Use Cases
- Structured Response Pattern: Follows a clear, step-by-step process for handling feedback: Read, Understand, Verify, Evaluate, Respond, Implement.
- Handling Ambiguity: Provides clear guidance on how to ask for clarification when feedback is unclear.
- External Reviewer Scrutiny: Outlines specific checks to perform on feedback from external sources before acceptance.
- YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary feature creep.
- Graceful Correction: Offers a method for acknowledging when your initial pushback was incorrect.
- Use Case: You receive a code review comment suggesting a significant architectural change. Instead of immediately agreeing, you use this Skill to verify the necessity, check for existing usage, and push back with technical reasoning if it conflicts with current project goals or your human partner's directives.
Quick Start
When receiving code review feedback, follow the structured response pattern to understand, verify, and then respond or implement.
