Author of Cloudflare's "Orchestrating AI Code Review at scale" blog post, Cloudflare.
Explore with your AI assistant
ChatGPT (opens in a new tab)Claude (opens in a new tab)Perplexity (opens in a new tab)Grok (opens in a new tab)
Opens a new chat with a prompt that points the assistant to this archive. What it writes is its own, not the archive's: check any quotation on its passage page before you rely on it. Or add the archive to your assistant as a connector: https://the-ai-record.com/mcp (how).
Byline author of Cloudflare's April 20, 2026 blog post on its internal AI code review system.
Why their word counts: Wrote the engineering post describing the system Cloudflare runs internally, with its own usage data.
Profile from this source, checked 2026-11-04.
Before the changes, authors acted on 34% of the code quality reviewer's serious findings. Now it's 59%.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, 
Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026, at Review quality.
With code quality at high effort, the average review now costs just $0.77, down 68% from the $2.43 it averaged over our two most expensive weeks before we started.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026.
Important findings per review went from 0.28 before to 0.30 now, and the intervals overlap.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026, at Review quality.
Before switching all reviews over from v1 to v2, we ran every review in every canary repo on both v1 and v2 in a comparative shadow mode. The two agreed on the approval decision in 98% of the merge requests we tested, so we moved everyone over in one go in early October and removed the v1 code.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026, at What else has changed since our last post?.
On the cost side, the average review costs $1.19 and the median is $0.98. The distribution has a long tail of expensive reviews – massive refactors that trigger full-tier orchestration. The P99 review costs $4.45, which means 99% of reviews come in under five dollars.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at Show me the numbers! / The overview.
In the first 30 days, the system completed 131,246 review runs across 48,095 merge requests in 5,169 repositories. The average merge request gets reviewed 2.7 times (the initial review, plus re-reviews as the engineer pushes fixes), and the median review completes in 3 minutes and 39 seconds.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at Show me the numbers! / The overview.
That is fast enough that most engineers see the review comment before they have finished context-switching to another task. The metric we’re the proudest about, though, is that engineers have only needed to “break glass” 288 times (0.6% of merge requests).
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at Show me the numbers! / The overview.
In a later randomized split, Opus 5.5 at medium showed no measurable change in review outcomes or critical findings compared with Opus 5, so we switched.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026, at Changing models and effort.
Medium effort did lose real findings. In the randomized split, code quality at medium led to roughly a quarter as many acted-on findings as at high, which is why we're moving it to high.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Cutting our inference bill by 68% by being obsessive about optimization, Cloudflare blog, October 19, 2026, at Review quality.
The bias is explicitly toward approval, meaning a single warning in an otherwise clean MR still gets approved_with_comments rather than a block.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at The coordinator helps keep things focused.
We've been running this system internally across tens of thousands of merge requests. It approves clean code, flags real bugs with impressive accuracy, and actively blocks merges when it finds genuine, serious problems or security vulnerabilities.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at Introduction.
Today, when an engineer at Cloudflare opens a merge request, it gets an initial pass from a coordinated smörgåsbord of AI agents. Rather than relying on one model with a massive, generic prompt, we launch up to seven specialised reviewers covering security, performance, code quality, documentation, release management, and compliance with our internal Engineering Codex. These specialists are managed by a coordinator agent that deduplicates their findings, judges the actual severity of the issues, and posts a single structured review comment.
Ryan SkidmoreAuthor of Cloudflare's "Orchestrating AI Code Review at scale" blog post · Practitioner, Cloudflare
Context. Describes the system as deployed on internal merge requests.
Post: Orchestrating AI Code Review at scale, Cloudflare blog, April 20, 2026, at Introduction.