How the Claude Code team thinks about verification · Addy Osmani · claude.dev (Anthropic), November 16, 2026
The Claude Code team keeps its checks out of reach of the changes they judge
Osmani writes that about 90% of the team's code is written and reviewed by Claude, and describes the gates that make that workable. Code Review reads REVIEW.md from the base branch, never from the pull request, because "If a change can modify the check that judges it, the check is broken." A 39-item reliability checklist gives each item a trigger that can be read from a diff, and Claude checks only the matching items, usually 3 to 10. If a check still fails after three rounds of fixes, Claude stops and brings in a human. A commit gate that can block commits whose session lacked /code-review or /verify has off, observe and enforce modes, and new gates start in observe. Claude may not skip a flaky test, add sleeps or retry it until it passes; if it cannot find the root cause, it deletes the test and writes down why.
The post gives one figure: in internal testing on structured file generation, a separate grader checking work against a rubric improved task success "by up to 10 points" over a standard prompting loop. That is Anthropic's number for its own tool, and the post does not publish the underlying data.
Why it matters: The cheapest rules to copy are loading gate rules from a branch the change cannot touch, triggering reliability checks from the diff, and running any new gate in observe mode before it blocks. Osmani names end-to-end, property and differential tests as the ones worth investing in; property and differential testing both did well in Luu's eval above.