What problem does it solve?
This Skill provides a rigorous framework for receiving and acting on code review feedback, preventing blind implementation or performative agreement. It ensures technical correctness, verifies suggestions against the codebase, and guides reasoned pushback when feedback is unclear or questionable, fostering a culture of technical rigor.
Core Features & Use Cases
- Structured Response Pattern: Guides you through reading, understanding, verifying, evaluating, and responding to feedback.
- Technical Rigor: Emphasizes verification against codebase reality and technical soundness over social comfort.
- Unclear Feedback Handling: Explicitly instructs to stop and ask for clarification before implementing.
- Reasoned Pushback: Provides guidelines for technically pushing back on suggestions that are incorrect, violate YAGNI, or conflict with architectural decisions.
- Use Case: You receive code review feedback. Use this Skill to systematically evaluate each suggestion, ensuring you understand its implications, verify its correctness for your specific codebase, and implement fixes effectively without introducing new issues.
Quick Start
Example: Handling unclear feedback
Reviewer: "Fix items 1-6"
You understand 1,2,3,6. Unclear on 4,5.
Correct Action: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."
(Do NOT implement 1,2,3,6 before clarifying 4,5)