How the Claude Code Team Verifies the 90% of Code That Claude Writes
Verification is the difference between running one Claude at a time and running dozens in parallel. This workflow shows how to make an AI reviewer trustworthy by constraining where rules live, capping reruns, and measuring recall in stages; without these controls, AI-written code can pass tests while the product breaks.
Anthropic's Claude Code team no longer reads every diff line. Instead, it defines what "done" means, writes checks that run the app, and inspects the evidence. The team has Claude verify changes by actually starting and operating the application through a skill named verify, which runs before every commit. Claude Code now ships a built-in /verify command and, since v2.1.286, the commit instruction enforces this pre-commit run unless the change is docs-only or tests-only.
The team keeps its reviewer honest by placing rules on branches the changes cannot modify. A 39-item reliability checklist, built from past incidents, tells Claude which risks to check for a given diff, typically 3 to 10 items. If a check fails three consecutive times, Claude hands off to a human with the reason stated. REVIEW.md on the protected default branch customizes the managed code review, while local /code-review reads CLAUDE.md instead. Commit gates start in observe mode to record would-be blocks before enforcing, with an escape hatch after two blocks.
The team evaluates its reviewer by measuring recall in three stages: raw discovery, after verification, and final review. Missed bugs become rules via pattern detection or replay of known incidents. Two numbers in the post are not the team's own: "up to 10 percentage points" comes from a Managed Agents test, and "two to three times" is Boris Cherny's personal estimate. The original post gives no effect numbers for its own verification stack.
The insistence that checks live on branches the change cannot modify is the core difference from typical agentic coding setups: an AI that can edit its own rubric will grade itself leniently.
Measuring recall in three stages rather than one end-to-end score is a smart move: it surfaces whether the system loses already-found bugs in the middle, which a single number would hide.
The commit gate's observe mode treats a process change like a code change with a rollout, letting a team validate false positives before enforcing.
The 39-item checklist format (trigger, check, incident) makes past knowledge executable for an agent without requiring humans to remember incidents.