Code Review Reception

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

Reception sequence

Understand: Read the complete feedback and identify each requested outcome and affected work. Restate requirements when needed; record unclear items for investigation.
Verify: Check findings against code, tests, agreed behavior, and the technical checks below. Identify supporting evidence and its limits before accepting or rejecting a suggestion.
Classify: Assign each finding to the categories below so its correction addresses the cause.
Resolve decisions: Apply the decision and dependency rules below. An item is ready only when its meaning, evidence, and any consequential decision are settled.
Dispatch corrections: Give the implementer each settled item's requirement, evidence, classification, affected tasks, and acceptance checks. Correct one item at a time: blocking issues (breaks, security), simple fixes (typos, imports), then complex fixes (refactoring, logic). Test each fix and verify affected functionality for regressions.
Report evidence: Inspect the resulting diff and verification output. Report what changed, which findings are resolved, and remaining blocked items or evidence gaps; use the factual-response policy below.