code-reviewlisted

# Code Review ## Purpose Answer whether an implementation approach is reasonable and safe, independently from whether tests happen to pass. ## Trigger Run after code changes, before a Quality Gate, after integration, or when architecture/security/performance risk requires independent assessment. ## Inputs - Exact base/head revisions, diff, changed paths, declared scope, and intended behavior. - Requirements, architecture, Contracts, Project Constraints, risk/impact, and current validation evidence. - Workflow Level, known deviations, and prior findings. ## Prerequisites - Reviewer is independent when required and defaults to read-only. - Build/test evidence corresponds to the reviewed revision. - Review scope and exclusions are explicit. ## Procedure 1. Classify review depth from change risk: - Small isolated change: Quick Review. - Normal module change: Code Review plus architecture consistency. - Cross-boundary/high-risk change: add Architecture, Security, Performance, or Integration Review as applicable. 2. Inspect the diff first, then affected call paths, data flows, trust boundaries, errors, and surrounding tests. 3. Check correctness risks, maintainability, cohesion/coupling, code smells, and scope discipline. 4. Check Requirement, architecture, Contract, API, compatibility, and Project Constraint compliance. 5. Check validation/error/recovery behavior and resource management. 6. Assess security and performance claims proportionally to exposure. 7. As