How the Claude Code team does code review(claude.dev)
456 points by pretext 9 days ago | 456 comments
tl;dr: Anthropic's Claude Code team handles AI-generated code volume (merged PRs doubled June-September, reverts dropped 40%) by shifting most review to automated layers: pre-PR agent verification, AI code review, blocking security scans, CI checks, risk-tiered human approval, and merge queues with feature flags for fast rollback. Humans focus on judgment calls—scope, architecture, risky code, and ownership—rather than reading every diff, while past incidents become evals to continuously improve the reviewer. Key lessons include capping review rounds to prevent agent-vs-agent loops and measuring noise by tracking how authors respond to comments.
HN Discussion:
  • ↓Anthropic's practices don't generalize to smaller teams and reflect their unique token/resource privilege
  • ↓The article itself appears AI-written, undermining its credibility and tone
  • ↓Abandoning human mental models of the codebase prevents long-term architectural reasoning
  • ↓Meaningful review and comprehension are impossible at 30k PRs/day; this is churn, not engineering
  • ↓Letting LLMs write and merge things like docs without human reading is reckless