receiving-code-review

Receiving Code Review - A Guide to Technically Rigorous Code Review Responses

Skill Overview

Receiving Code Review is a code review response skill focused on technical validation. It helps developers perform a rigorous technical assessment of review feedback—rather than offering performative agreement or implementing blindly.

Use Cases

1. You Receive Unclear or Vague Code Review Feedback

When review comments are ambiguous, lack context, or are hard to understand, this skill guides you to pause implementation, proactively ask for clarification, and avoid incorrect implementation caused by partial understanding.

2. You’re Facing Technical Suggestions from External Reviewers

For code review suggestions coming from outside the project or the team, this skill provides a systematic validation process to determine whether the advice applies to the current codebase’s technical stack, architectural constraints, and business requirements.

3. You Need to Technically Validate Review Comments

When the proposed changes might break existing functionality, conflict with established architecture, or are technically infeasible, this skill guides you on how to reasonably challenge the feedback and communicate using technical reasoning.

Core Capabilities

1. A Six-Step Response Workflow

It provides a standardized response pattern—READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT—to ensure every piece of feedback undergoes a complete technical validation process and to prevent blind implementation.

2. Source-Based Handling

It distinguishes feedback from trusted partners versus external reviewers. For external suggestions, it uses a “skeptical but careful” strategy, including a five-item validation checklist, to ensure the technical correctness and applicability of the advice.

3. Forbidden Response Modes

It clearly defines performative phrases to avoid (e.g., “You’re absolutely right,” “Great suggestion”) and offers technical alternatives, emphasizing demonstrating your understanding through actions and code changes.

FAQs

Should I implement the code review feedback immediately?

No. This skill requires you to fully read the feedback, understand the requirements, validate technical feasibility, and evaluate the impact on the codebase before implementation. Only after confirming the suggestion is correct and applicable should you gradually implement it. For any unclear items, ask for clarification before implementing to avoid incorrect changes due to partial understanding.

When should I question a code review suggestion?

You should challenge a suggestion when it may break existing functionality, violate the YAGNI principle (proposing “professional” features that aren’t actually used), is technically incorrect for the current tech stack, involves legacy or compatibility constraints, or conflicts with the project’s architectural decisions. This skill provides specific methods for questioning and communication strategies.

How should I handle unclear or vague code review feedback?

If you receive unclear review comments, stop implementation immediately and proactively ask for clarification. Don’t implement only what you understand while leaving the unclear parts as-is, because multiple review items may be interrelated. The right approach is to clearly state which items you’ve understood and which ones require clarification, and then implement everything together after you reach a complete understanding.