What problem does it solve?
Receiving code review feedback often triggers performative agreement or blind implementation of suggestions, leading to broken functionality, wasted effort, and technical debt when feedback is incorrect, unclear, or misaligned with the codebase's existing architecture.
Core Features & Use Cases
- Technical Verification First: Mandatory check of all feedback against the actual codebase to confirm correctness, compatibility, and alignment with existing architecture before any implementation.
- Structured Response Framework: Clear rules for handling unclear feedback, pushing back on incorrect suggestions, and avoiding performative agreement or gratitude expressions that add no value.
- Use Case: When a reviewer suggests removing a legacy API endpoint, use this skill to first check if the endpoint is actively used in the codebase, confirm backward compatibility requirements, and push back with technical reasoning if removal would break existing functionality, rather than agreeing and implementing a breaking change.
Quick Start
When you receive code review feedback with multiple items, first ask for clarification on any unclear points before implementing any changes, and verify each suggestion against the codebase to confirm it will not break existing functionality.
