Code Review

Deliver one bounded review with evidenced, actionable findings or a defensible clean result. Apply the implementation, system, design, and diet perspectives proportionately; no finding is preferable to a speculative one.

Scope and guidance

Use the named files, subsystem, branch, commit, PR, or diff. A roadmap, specification, issue, ADR, or migration review covers its governed implementation, not just the document. Establish the intended outcome, claimed milestone, implementation range, and edit policy. Without a named target, use uncommitted changes when present; ask only if no target can be inferred.

Read the implementation lens for the core review and safe-fix policy. Load the other detailed lenses when their dimensions are material to the target: