What problem does it solve?
This Skill solves the common issue of unprofessional and technically risky responses to code review feedback, which often lead to broken functionality, unnecessary code changes, or damaged team relationships from performative agreement or blind implementation of unvetted suggestions.
Core Features & Use Cases
- Structured 6-Step Response Workflow: Guides you to read, understand, verify, evaluate, respond, and implement feedback one item at a time to avoid errors.
- Scenario-Specific Guidance: Includes rules for handling feedback from your human partner vs external reviewers, unclear multi-item feedback, and YAGNI checks for unused proposed features.
- Professional Interaction Rules: Teaches how to push back with technical reasoning instead of defensiveness, acknowledge correct feedback without performative praise, and reply to GitHub PR inline review comments properly.
- Use Case Example: If a reviewer asks you to remove legacy code, this Skill guides you to first check if the code is required for backward compatibility before deleting it, instead of agreeing blindly.
Quick Start
When I receive code review feedback, follow the Skill's steps to verify each suggestion is correct for our codebase before implementing anything, and ask for clarification on any unclear points first.
