Code Review Reception

Overview

Code review requires technical evaluation, not emotional performance.

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

Routing Boundary

Use this skill only when feedback already exists and must be evaluated. A fresh request like "review this PR" belongs to code-reviewer; a request like "run OWASP security audit" belongs to security-reviewer.

The Response Pattern

WHEN receiving code review feedback: