receiving-code-review

What problem does it solve?

Receiving code review feedback can be challenging, often leading to performative agreement, blind implementation, or unclear communication. This skill enforces a rigorous, technical approach to receiving feedback, mandating verification before implementation, clarifying unclear items, and providing reasoned pushback when necessary, ensuring technical correctness over social comfort.

Core Features & Use Cases

• Technical Verification: Requires verifying feedback against codebase reality before implementing.
• Clarification Protocol: Guides asking for clarification on unclear items before proceeding.
• Reasoned Pushback: Provides guidance on when and how to technically push back on questionable suggestions.
• No Performative Agreement: Explicitly forbids emotional or performative responses, focusing on technical facts.
• Use Case: When you receive code review feedback, use this skill to systematically process each item, ensuring you understand, verify, and respond technically, leading to better code and clear communication.

Quick Start

Use the receiving-code-review skill to process the feedback on the 'user-authentication' pull request.