Code Review Reception

What problem does it solve?

Blindly implementing code review feedback or engaging in performative agreement can introduce new bugs, ignore critical context, or lead to unnecessary work. This skill establishes a rigorous, technical process for receiving and evaluating code review feedback, ensuring that all changes are technically sound and aligned with project goals.

Core Features & Use Cases

• Structured Response Pattern: Guides you through reading, understanding, verifying, evaluating, and responding to feedback.
• Technical Verification: Emphasizes checking suggestions against codebase reality, existing functionality, and architectural decisions before implementation.
• Reasoned Pushback: Provides guidance on when and how to technically challenge feedback that might be incorrect or misinformed.
• Use Case: When you receive code review comments on your pull request, you'll use this skill to systematically evaluate each suggestion, clarifying unclear points, verifying technical correctness, and implementing only the changes that genuinely improve the codebase.

Quick Start

When receiving feedback, follow the pattern:

1. READ all feedback without reacting.

2. UNDERSTAND by restating or asking.

3. VERIFY against codebase reality.

4. EVALUATE for technical soundness.

5. RESPOND with technical acknowledgment or pushback.

6. IMPLEMENT one item at a time, testing each.

Example of acknowledging correct feedback:

"Fixed. Added missing help text in CLI wrapper."