Receiving Code Review

协作类

Use when receiving code review feedback, before implementing suggestions, especially when feedback seems unclear or technically questionable.

Quick Start

Understand in 30 Seconds

Code review requires technical assessment, not emotional performance. Verify before implementing.

When to Use

Received code review feedback
Feedback seems unclear or questionable
Need to decide how to handle suggestions

Complete Guide

Core Principle

Core Principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

Response Pattern

Read: Full feedback, don't react
Understand: Restate requirement in own words (or ask)
Verify: Check against codebase reality
Evaluate: Is this technically sound for this codebase?
Respond: Technical confirmation or reasoned rebuttal
Implement: One item at a time, test each

Forbidden Responses

Never:

"You're absolutely right!" (performative)
"Good point!" / "Excellent feedback!" (performative)

Instead:

Restate the technical requirement
Ask clarifying questions
Start working directly (actions > words)

When to Push Back

Push back when:

Suggestion breaks existing functionality
Reviewer lacks complete context
Violates YAGNI (unused features)
Technically incorrect for this tech stack

requesting-code-review - Request code review