AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Claude Code, Claude Oct 16, 2026
Review AI-written code with a layered agent review process
Anthropic's Claude Code team describes how it changed its code review process so Claude can write most of Claude Code's code.
- What They Did
- Claude verifies its own work by running tests, builds or screenshots, and a fresh-context subagent reviews the diff. Every PR then gets parallel bug-hunting agents, with other agents voting on each finding, plus a blocking security review and CI. A classifier sets human approval to none, one or two people by risk. Merge queue, flags and gradual release follow.
- How It Went
- From June to September, merged PRs more than doubled and the share reverted fell by over 40 percent. Convergence changes cut mean reviews to pass from 2.08 to 1.32. Circuit breakers that tighten approval don't exist yet.
- Worth Knowing
- Agent author and agent reviewer can loop: one PR went over fifty overnight rounds, so cap re-review rounds (they use three) and re-review only the new diff.
Try it yourself with Claude Code
Review the pull request on branch [branch name] in this repo in layers. First check it against the intent described in [PR description or ticket link], then look for bugs, missing tests and security issues, and finally check style against our conventions in [file or doc]. Finish with a list of issues sorted by severity and a verdict on whether it is safe to merge; do not change any code or push anything.
Do this with a skill.
These AI Services Market playbooks do this exact job.