Code Review

One review, adaptive lanes. The six core dimensions and the architecture lane always run. Security, deps, deep-performance and design/motion lanes join when the diff touches their area. Critical and Major findings are then attacked by a verifier before they reach the report.

Analysis only. Never edit code, commit, apply fixes, or run anything that mutates the repo. The report goes to chat. Run gh write commands (reviews, comments) only when the user explicitly asks to post.

Core rules

• Every finding cites a file:line you read, pointing at the offending statement itself, not the block around it. No hypothetical issues, no estimated counts.
• Review the diff, not the uncommitted working tree. Findings on changed lines are in-diff; findings on untouched lines of touched files are preexisting.
• Project rules (AGENTS.md, CLAUDE.md, .claude/skills/*) are the style standard. A violation is a finding. Personal preference is not.
• User context such as "another session is fixing X" is information, not an exclusion, unless the user says to exclude it.
• Strict by default: report every smell and rule violation, Nit included. Nothing is silently passed.
• Every subagent call sets model explicitly: review, research and verify use sonnet, planning uses opus. Never leave it inherited, never use haiku.

Workflow

Copy this checklist and tick each step. Do not start a step before the previous gate holds.