Skip to content
claude.dev BlogAddy Osmani, Morgan Westlee Lunt, and Qing Wang

How the Claude Code team does code review

The Claude Code team hands most code reading to automated review, sets human approval by risk level, and controls errors with staged rollouts and fast rollbacks. From June to September, merged PRs more than doubled while the share needing rollback fell more than 40%. Low-risk changes can merge after automated checks pass with no human approval; medium and high risk need one and two approvers. Past incidents feed a daily eval, and review that reaches three rounds forces the team to reconsider the approach.

Why it matters: The team chains automated review, risk tiers and fast rollback into one process, saving human approval for high-risk changes and feeding incidents back into review.

Read the original ↗Export Markdown