Receiving Code Review

Receiving code review requires technical evaluation, not emotional performance. This skill governs what happens between getting feedback and typing the first edit — not how to produce a review.

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

When to Use

• You just received review comments (from a human, code-review, review, or pr-multi-perspective-review) and are about to act on them
• Feedback includes multiple items and some are unclear or only partially understood
• A suggestion seems plausible but you have not yet checked it against this codebase
• You pushed back earlier and now have evidence the reviewer was actually right

When NOT to Use