Overview

Code review requires technical evaluation, not emotional performance. Verify before implementing and ask before assuming.

How This Skill Works

Follow the six-step Response Pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT. Each step anchors a concrete action (read feedback fully, restate requirements, check against the codebase, assess technical fit, acknowledge or push back, and implement changes one item at a time with tests). Tool Use: Referenced by implementation processes when handling review feedback.

When to Use It

• When you receive code review feedback that may affect functionality
• When the reviewer lacks full context and you need clarifications
• When a suggested change could violate YAGNI or architectural decisions
• When feedback requires validation against tests and existing code
• When you want to implement suggestions incrementally and test after each change

Quick Start

1. Step 1: READ the received feedback in full.
2. Step 2: UNDERSTAND and VERIFY against the codebase and tests.
3. Step 3: IMPLEMENT changes one item at a time and validate with tests.

Best Practices

• Read feedback in full before reacting
• Restate the requirement to confirm understanding
• Verify suggestions against the real codebase and tests
• Evaluate the technical impact and alignment with architecture
• Implement changes one item at a time and test after each

Example Use Cases

• A reviewer asks to change a function's API; you read the feedback, restate the requirement, verify how it affects callers, evaluate alternatives, respond with a reasoned pushback if the change is unnecessary, and implement incrementally with tests.
• A request to remove a legacy check is made; you verify its cross-module impact before removing and updating tests accordingly.
• Feedback lacks context about a module; you push back with clarifying questions while validating assumptions against the codebase.
• An optimization suggestion breaks existing integration tests; you verify against tests and architecture before implementing.
• You identify a YAGNI-driven suggestion; you push back with a minimal alternative and implement only the essential changes.

Frequently Asked Questions