Claude Sonnet 5 vs Kimi K3 for code review
Effectively a dead heat: 89–87
Same 12 code review tasks, marked blind by three rival labs. Claude Sonnet 5 took 6 tasks, Kimi K3 took 3, 3 tied. Tested 18 Aug 2026.
Where they differed most
Review this function. Context you can rely on: `page` is 1-based — the public API docs promise that page=1 returns the first page; `items` is always an array and may be empty; `perPage` is taken straight from a query string. function pageOf(items, page, perPage) { const start = page * perPage; const rows = items.slice(start, start + perPage); const lastPage = Math.ceil(items.length / perPage); return { rows, total: items.length, lastPage, hasNext: page <= lastPage }; } List the real defects, most damaging first, and for each one say what a user of the API would actually SEE — not what the code does, what they notice. Then give the corrected function. Do not list style preferences as defects.
## Defects, most damaging first **1. `start = page * perPage` — page=1 doesn't return the first page** Since `page` is documented as 1-based, `page=1` should map to `start=0`. Instead `start = 1 * perPage`, which skips the entire first page. **What the user sees:** They call the API with `page=1` (per the docs, "the first page") and get back the *second* page of data. The first `perPage` items are never retrievable through the API at all — no combination of page numbers ever returns them. This silently corrupts every paginated response and vi…
# Defects
**1. Off-by-one: `start = page * perPage` skips the entire first page of data.**
With a 1-based API, page 1 must start at index 0; this starts at index `perPage`. What the user sees: they request page 1 and the first `perPage` records are simply missing — and they never appear on *any* page, so those records are unreachable through the documented API. Meanwhile `total` still counts them, so the numbers don't add up ("total: 100" but only 90 items ever show up). Additionally, the final page is *always* empty, because `lastPage * perPa…Task by task
| Task | Claude Sonnet 5 | Kimi K3 |
|---|---|---|
| The pagination that skips page one | 6 | 9 |
| Nothing wrong with it | 8 | 5 |
| Three things wrong in six lines | 8 | 9 |
| Two customers, one last item | 9 | 9 |
| Rank by what breaks | 10 | 9 |
| The review, as JSON | 9 | 8 |
| Slow is not the same as wrong | 10 | 9 |
| Overdue at one in the morning | 9 | 9 |
| Write only the comment | 10 | 10 |
| The complaint that is not a defect | 8 | 9 |
| Right, and unusable | 10 | 9 |
| Refuse the rubber stamp | 10 | 9 |
Full receipts: Claude Sonnet 5, Kimi K3 · judges gemini-3.1-pro-preview, gpt-5.6-terra, grok-4.5
Questions people ask
Which is better for code review: Claude Sonnet 5 or Kimi K3?
Effectively a dead heat: Claude Sonnet 5 edged it 89/100 to 87/100 on our code review suite — too close to matter, so pick on price or the product you already use.
How was this tested?
Both models answered the identical published code review tasks. Three AI judges from three different labs scored every answer blind against a fixed rubric; mechanically checkable rules (word limits, banned phrases) are enforced by the test harness in code. The raw outputs and judge verdicts are downloadable.
More code review head-to-heads: Claude Sonnet 5 vs GPT-5.6 Sol · GPT-5.6 Sol vs Kimi K3 · Claude Sonnet 5 vs GPT-5.5 · GPT-5.5 vs Kimi K3 · Claude Sonnet 5 vs Grok 4.5 · Claude Sonnet 5 vs GLM 5.2
Full ranking: Best AI for code review · model pages: Claude Sonnet 5, Kimi K3