An open, practical comparison of code-review models in one real review harness. Quality first, then completion, speed, and cost.
Current recommendation
Claude Opus 5 currently ranks first at 80% known-issue recall and 25.4% AI-assessed provisional precision. Muse Spark 1.2 follows at 78.3% recall. Completion, speed, cost, provider behavior, and each row's limitations remain visible alongside quality.
anthropic/claude-opus-5 · Amazon Bedrock
meta/muse-spark-1.2 · Meta
z-ai/glm-5.3 · Fireworks
A reviewer earns credit for identifying an evidence-backed defect once. Rephrasing it, guessing loudly, or padding the review does not help.
Defect recall, precision, clean-review restraint, severity judgment, and consistency across repeated attempts.
One-to-one matching, proof-backed gold findings, clearly labeled evidence review, and visible uncertainty for incomplete labels.
Latency is reported after review quality, with failures and budget exhaustion kept separate from successful reviews.
Observed token and cost data where available. Unknown cost is null—never quietly treated as free.
Hold prompt, tools, budgets, context, scorer, and task release still. Change the model or provider endpoint.
Measure the whole review system: its model, prompt, tools, parsing, and orchestration. OpenRouter Review Bot and Grok Code Review Bot are first.
Current state
The current board is a small, 3-attempt model comparison—not a universal measure of coding ability. It is useful for choosing models in the OpenRouter Review Bot, and future runs can add harder cases and newly released models. When a row needs targeted repair, successful original reviews are preserved and only missing cells are rerun; that history and its all-in cost stay visible.