Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- Initial release of the skill for rigorous code review reception. - Outlines a step-by-step pattern for handling code review feedback, focusing on technical verification before implementation. - Specifies forbidden performative or uncritical responses; promotes technical acknowledgment or pushback. - Includes guidance for unclear feedback, source-specific review handling, and the YAGNI principle. - Provides practical examples, common mistakes, and correct formats for updates and replies. - Sets clear rules for interactions in collaborative tools like GitHub.