Driftproof

Report 013: Claude Sonnet 5.5, the day after its release

What did Report 013 find?

Release drift report. It measures a new model on the same skills and tasks. Beside that, it sets two current models side by side, and runs one model again, on a later day and a newer Claude Code, beside its Report 011 run.

How did each comparison come out, run by run?

With the skill, Claude Sonnet 5.5 was never clearly higher or lower than Claude Opus 5.5 in nine results, and five of them had too few answers to tell. It scored clearly higher than Claude Sonnet 5 on documentation in two of three runs.

comparison, with the skilltaskrun 1run 2run 3
Claude Sonnet 5.5 against Claude Sonnet 5code reviewtoo few answers to tellno clear differencetoo few answers to tell
Claude Sonnet 5.5 against Claude Sonnet 5git workflowtoo few answers to tellno clear differenceno clear difference
Claude Sonnet 5.5 against Claude Sonnet 5documentationclearly highertoo few answers to tellclearly higher
Claude Sonnet 5.5 against Claude Opus 5.5code reviewtoo few answers to telltoo few answers to tellno clear difference
Claude Sonnet 5.5 against Claude Opus 5.5git workflowno clear differenceno clear differenceno clear difference
Claude Sonnet 5.5 against Claude Opus 5.5documentationtoo few answers to telltoo few answers to telltoo few answers to tell
Claude Opus 5.5 against Report 011code reviewtoo few answers to telltoo few answers to telltoo few answers to tell
Claude Opus 5.5 against Report 011git workflowtoo few answers to telltoo few answers to telltoo few answers to tell
Claude Opus 5.5 against Report 011documentationtoo few answers to tellclearly higherclearly higher

The nine comparisons are three tasks times three pairings. Five of the nine comparisons did not give the same result in every repeat: Claude Sonnet 5.5 against Claude Sonnet 5 on code review, git workflow and documentation; Claude Sonnet 5.5 against Claude Opus 5.5 on code review; and Claude Opus 5.5 against Report 011 on documentation. Three of those five changed only between “too few answers to tell” and “no clear difference”: Claude Sonnet 5.5 against Claude Sonnet 5 on code review and git workflow; and Claude Sonnet 5.5 against Claude Opus 5.5 on code review.

Clearly higher (or lower): in that run the spread of scores for the two models did not overlap, and their averages were at least 0.05 apart. A model’s spread is its average plus or minus the usual variation of its answers’ scores.

No clear difference: there were enough answers to see a gap of 0.05, and the spreads overlapped or the gap was smaller.

Too few answers to tell: the scores were too spread out, or too few, to see a gap of 0.05 either way. It does not mean the models scored the same.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-2--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-3--code-review-and-quality.md; docs/reports/011/evidence/git-workflow-and-versioning-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-3--git-workflow-and-versioning.md; docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-2--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-3--documentation-and-adrs.md; config.js.

What did each model score, without the skill and with it?

Code review: each model’s average score in each run, without the skill and with itCode reviewClaude Sonnet 5Claude Sonnet 5.5Claude Opus 5.5
Git workflow: each model’s average score in each run, without the skill and with itGit workflowClaude Sonnet 5Claude Sonnet 5.5Claude Opus 5.5
Documentation: each model’s average score in each run, without the skill and with itDocumentationClaude Sonnet 5Claude Sonnet 5.5Claude Opus 5.5

Under each model’s name, one row per run, runs one to three from the top. The hollow dot is a model’s average score without the skill, the filled dot its average with the skill, and the line between them what the skill added in that run (red where the score went down). Scores run from zero to one. The faint lines mark four tenths at the left, then six and eight tenths, and a full score at the right. Each dot is the average over the model’s answers in that run, each answer scored three times by the grader. The positions are read from the twenty-seven receipts listed at the bottom of the page.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json.

What do the runs show?

Did Claude Sonnet 5.5 score differently from Claude Sonnet 5?

With the skill loaded, Claude Sonnet 5.5 scored clearly higher than Claude Sonnet 5 on documentation in two of three runs. On code review and git workflow it was never clearly higher or lower: each run gave no clear difference or too few answers to tell.

On code review, the skill moved Claude Sonnet 5.5’s average by +0.009, +0.051 and +0.034 in the three runs; without the skill it averaged 0.878, 0.849 and 0.861. For Claude Sonnet 5 the skill moved it by +0.302, +0.207 and +0.085. These figures are context, not a verdict.

Read from: docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json.

Did Claude Sonnet 5.5 score differently from Claude Opus 5.5?

With the skill loaded, Claude Sonnet 5.5 was never clearly higher or lower than Claude Opus 5.5, on any task in any run. Of those nine results, four showed no clear difference and in five there were too few answers to tell.

Without the skill, on git workflow, Claude Opus 5.5 averaged 0.508, 0.485 and 0.579, its answers varying widely (spreads of 0.287, 0.278 and 0.322), and Claude Sonnet 5.5 averaged 0.860, 0.850 and 0.857 (spreads of 0.009, 0.007 and 0.009). No test compared the two without the skill, so these averages are context, not a result.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md.

Did Claude Opus 5.5 score as it did in Report 011?

With the skill loaded, Claude Opus 5.5 scored clearly higher on documentation than in Report 011 in two of three runs; the other run had too few answers to tell. On code review and git workflow every run had too few answers to tell.

Report 011 was a single run, on an older Claude Code (2.1.280 against 2.1.284) and on a different day. Every answer in both reports was newly written by the model, so run-to-run variation alone can move a score. That is part of why this difference cannot be put down to Claude Code.

Read from: docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-3--documentation-and-adrs.md; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json.

Why run every test three times?

Repeat runs of the same test did not always agree: five of the nine comparisons gave a different result in one run than in another.

Claude Opus 5.5’s score on code review without the skill was 0.831, 0.857 and 0.713 across the three runs. One run alone could have told a different story.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-2--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-3--code-review-and-quality.md; docs/reports/011/evidence/git-workflow-and-versioning-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-3--git-workflow-and-versioning.md; docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-2--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-3--documentation-and-adrs.md.

What are the limits, and what differs from Reports 009 and 011?

What does this report not show?

Each skill was tested on one task only. Nothing here says how these skills do on other tasks, or how these models do at coding in general.

Each model answered each task between 3 and 9 times per run, and the grader scored every answer three times. That is few answers. Where a result had too few answers to tell, the scores were too spread out, or too few, to see a gap of 0.05.

Every answer was scored by claude-opus-5 as the grader, as in Reports 009 and 011. Our other reports use a different grader, set by the judge policy, so compare these scores with Reports 009 and 011 only.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; config.js.

What differs from Reports 009 and 011?

Claude Sonnet 5.5 came out on 28 Sep 2026, as the vendor’s announcement dates it (its record, release-date.json, is published beside this page). The first run began on 29 Sep 2026 at 03:53 UTC, the next day.

Every test ran three times instead of once. All three models ran on the same Claude Code, version 2.1.284; Report 009 used 2.1.272 and Report 011 used 2.1.280. No model was given an effort or thinking setting. Claude Code applied its own per-turn effort in every call of Claude Sonnet 5.5 and every call of Claude Opus 5.5, and in no call of Claude Sonnet 5.

Prices come from the vendor’s pricing page as saved on the day of the run: 2 and 10 dollars per million input and output tokens for both Sonnet models, and 4 and 20 for Claude Opus 5.5. Prices change the estimated cost only, never a score.

A safety limit allowed up to 360 model calls per run, where Report 011 allowed 240, because this report runs nine tests per run instead of six.

Read from: docs/reports/013/evidence/release-date.json; docs/reports/013/evidence/run-1/run-record.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/011/evidence/run-20260923T062806Z--run-record.json; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.surface.json; docs/reports/013/evidence/guard.py; docs/reports/011/evidence/guard.py.

Amendments

Amendment one: a new title, and the page rearranged for readers

Made on 30 Sep 2026, the day its source was saved.

The title. This report was first published as Report 013: Claude Sonnet 5.5 on release day, three skills, three runs. The vendor’s announcement dates Claude Sonnet 5.5 28 Sep 2026, and the first run began on 29 Sep 2026 at 03:53 UTC. So the runs were made the day after its release, and the title now says so: Report 013: Claude Sonnet 5.5, the day after its release. The announcement’s record is published beside this page as release-date.json, which is new in the published files.

The page. The page now opens with a short summary and one table of every comparison in every run, then a chart, four short readings, and the limits beside what differs. The full tables, the set-up, the run record and the files are folded at the bottom. No receipt, figure, file or result changed, and every figure is read from the same files. The results carry three plain labels in place of the runner’s four phrases: clearly higher or lower (separation detected, upward or downward), no clear difference (no separation detected), and too few answers to tell (not enough draws to conclude at this effect floor). The first version’s headline and four readings are kept below, as published.

Read from: docs/reports/013/evidence/release-date.json; docs/reports/013/evidence/run-1/run-record.json.

The first version’s headline and four readings, as published

Claude Sonnet 5.5 on the three skills and cases of Reports 009 and 011, beside fresh Claude Sonnet 5 and Claude Opus 5.5 arms on one Claude Code version, each arm run three times. Read by the runner’s own comparison of the with-skill arms, run by run: against Claude Sonnet 5, documentation-and-adrs reads separation upward in two of three runs, and code-review-and-quality and git-workflow-and-versioning read separation in zero of six; against Claude Opus 5.5, the three skills read separation in zero of nine.

Every figure below is read from a receipt or a file published beside it, and each block names its files. The target model of the new arm is claude-sonnet-5-5, and every draw of every arm was judged by claude-opus-5. This report measures what a skill adds to each model on these cases. It makes no claim about any model’s coding ability.

Read from: docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md.

Four readings

1. With the skill, Claude Sonnet 5.5 separates upward from Claude Sonnet 5 on documentation-and-adrs in two of three runs, and downward in zero of nine readings. On code-review-and-quality and git-workflow-and-versioning it detects separation in zero of six readings, and in three of those six readings the draws could not have told. What the skill adds is another matter: on code-review-and-quality Claude Sonnet 5’s lift is +0.302, +0.207, +0.085 across the runs and Claude Sonnet 5.5’s +0.009, +0.051, +0.034, because Claude Sonnet 5.5 without the skill already reads 0.878, 0.849, 0.861, against Claude Sonnet 5’s 0.578, 0.674, 0.573. So on these cases the rule reads no downward separation in the upgrade, on any skill in any run, and on code-review-and-quality Claude Sonnet 5.5’s lift is the smaller in every run, from a higher score without it. The runner’s comparison of two receipts reads no lift, so that second part is context, not a verdict.

2. With the skill, the rule separates Claude Sonnet 5.5 from Claude Opus 5.5 in zero of nine readings; the lifts differ where the baselines do. Of the nine readings, five are not enough draws to conclude at this effect floor. On git-workflow-and-versioning Claude Opus 5.5’s lift is +0.353, +0.371, +0.276 and Claude Sonnet 5.5’s +0.000, +0.013, +0.007; with the skill the rule detects separation in zero of three runs, and without it Claude Opus 5.5 reads 0.508, 0.485, 0.579 where Claude Sonnet 5.5 reads 0.860, 0.850, 0.857. On documentation-and-adrs both lifts are above zero in every run: Claude Sonnet 5.5 by +0.208, +0.238, +0.272, Claude Opus 5.5 by +0.116, +0.300, +0.322. So on these cases the skill does not take Claude Sonnet 5.5 to a with-skill score the rule can tell apart from Claude Opus 5.5’s, and how much it adds depends on where each model starts without it. The runner does not compare lifts, and none of this is a statement about either model’s coding ability. Each receipt’s own reading of its lift is on its receipt page; a lift is context here, and none is read as a gain.

3. Claude Opus 5.5 on this report’s Claude Code separates from Report 011’s receipts upward on documentation-and-adrs in some runs and not others. On documentation-and-adrs the rule reads separation upward in two of the three runs, against Report 011’s single run, whose spread there was 0.148. On code-review-and-quality and git-workflow-and-versioning it detects separation in zero of six readings. Report 011 is one run, and this report’s own runs differ from each other, so this is a statement about these draws on two Claude Code versions and two dates, not about Claude Code.

4. The runs differ from each other, which is why there are three. Of the nine skill and comparison pairs, five read a different verdict in one run than in another. Claude Opus 5.5’s baseline on code-review-and-quality read 0.831, 0.857, 0.713 across the three runs. Claude Sonnet 5’s with-skill arm on the same skill read 0.657 ± 0.257 (4 draws) in run 3, against 0.880 ± 0.006 (3 draws) and 0.881 ± 0.005 (3 draws) in the other two. A reading from one run of one case is one reading; the counts above say how often it came back.

Read from: docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md; docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-2--documentation-and-adrs.md; docs/reports/013/evidence/diff--harness--run-3--documentation-and-adrs.md; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-2--code-review-and-quality.md; docs/reports/013/evidence/diff--harness--run-3--code-review-and-quality.md; docs/reports/011/evidence/git-workflow-and-versioning-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/diff--harness--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/diff--harness--run-3--git-workflow-and-versioning.md.

Amendment two: headings that state their questions

Made on 1 Oct 2026.

Each section heading of the report body above its Amendments now states the question the section answers. No receipt, figure or result changed, and no sentence of the report body. A link made to a section before this amendment still lands on it. This amendment’s record is added to the evidence below. The headings as first published, and what each now reads:

  • Every comparison, every run now reads How did each comparison come out, run by run?
  • Every run, without the skill and with it now reads What did each model score, without the skill and with it?
  • What the runs show now reads What do the runs show?
  • Sonnet 5.5 against Sonnet 5 now reads Did Claude Sonnet 5.5 score differently from Claude Sonnet 5?
  • Sonnet 5.5 against Opus 5.5 now reads Did Claude Sonnet 5.5 score differently from Claude Opus 5.5?
  • Opus 5.5 against Report 011 now reads Did Claude Opus 5.5 score as it did in Report 011?
  • Why three runs now reads Why run every test three times?
  • Limits, and what differs from Reports 009 and 011 now reads What are the limits, and what differs from Reports 009 and 011?
  • Limits now reads What does this report not show?
  • What differs now reads What differs from Reports 009 and 011?

Read from: docs/reports/013/evidence/amendment-2.json.

Amendment three: the runner’s phrase that amendment one left out

Made on 1 Oct 2026.

Amendment one says the plain labels replace the runner’s four phrases. The runner has five: the list leaves out below effect floor. This page labels that result no clear difference, as it labels no separation detected, unless there were too few answers to tell.

Amendment one is not changed, because a published amendment only grows. No receipt, figure, label or result changed. This amendment’s record is added to the evidence below.

Read from: docs/reports/013/evidence/amendment-3.json.

Evidence and files

How the runs were set up, in full: limits, departures and what stayed fixed, as first published

Limits, read these first

  • One case per skill. Each receipt carries a suite of 1, 1, 1 case, in the order code-review-and-quality, git-workflow-and-versioning, documentation-and-adrs, the cases Reports 009 and 011 used. Nothing on this page describes how any of the three skills behaves on any other task, or how any of the three models behaves in general.
  • Few draws. Each arm drew between 3 and 9 generations, each judged 3 times, and each case’s band is the spread across its draws. With one case there is no spread across cases, and each receipt records its combined uncertainty on the lift as absent, single_case.
  • Three runs, and a verdict is read in one run at a time. Reports 009 and 011 ran each arm once. This report runs every arm three times, one after another, with the same script and settings, because one run’s figure can move in the next: Report 011’s Claude Opus 5.5 baseline on code-review-and-quality read 0.68, and the same arm in this report’s run 1 read 0.83. Each verdict below is the runner’s comparison of two receipts from one run. Across the three runs the page counts those verdicts; it pools no draws and reads no verdict across runs.
  • The judge is not one of the three arms, and it is Report 009’s. Every draw was judged by claude-opus-5, as in Reports 009 and 011. It is not the judge the judge policy fixes for Driftproof’s reports, so these figures are comparable with Reports 009 and 011 and not with Reports 001 to 008.
  • A verdict reads the with-skill arms only. The runner’s comparison of two receipts sets one receipt’s with-skill band against the other’s, per case. The second question is about lift, what the skill adds over the same model without it. The runner does not compare lifts, so the lifts are shown as context and no verdict on this page is read from them.
  • The harness check moves more than Claude Code. It sets Report 011’s Claude Opus 5.5 receipts, one run on an older Claude Code, beside this report’s three Claude Opus 5.5 runs. The date changed too, and every generation is a fresh draw, so a separation there could not be put down to the Claude Code version alone. Report 011’s sidecars record no per-call effort state, so whether Claude Code applied a per-turn effort there, as it did in all of this report’s Claude Opus 5.5 calls, is not known.
  • Verification levels. All 27 receipts of this report are TESTED, each answered by a model the surface attested (answered_by.kind model in every one).

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json.

What departs from Reports 009 and 011

  • One Claude Code version for every arm. Every call of every arm ran on Claude Code 2.1.284, installed at the npm integrity the run record states. Report 009 ran on 2.1.272 and Report 011 on 2.1.280. The runner writes no Claude Code version into a receipt, and a receipt is sealed, so each receipt has a sidecar, <receipt>.surface.json, bound to it by its receipt_hash and recording the version each of its calls reported: 2.1.284 in all of them.
  • Effort and thinking at Claude Code’s defaults. No arm was given an effort or thinking setting, as in Reports 009 and 011. Each call’s first event records whether Claude Code applied a per-turn effort, and the sidecars carry it: claude-sonnet-5-5 true in all 61 of its generation calls across the three runs; claude-sonnet-5 false in all 68 of its generation calls across the three runs; claude-opus-5-5 true in all 75 of its generation calls across the three runs. The judge’s calls read false. So the arms ran on the same surface with each model’s own default, and not at one effort.
  • The prices are this run’s own. The runner’s registry had no row for claude-sonnet-5-5. This run used a copy of it with that row added at 2 and 10 dollars per million input and output tokens, claude-sonnet-5 at 2 and 10, and claude-opus-5-5 at 4 and 20, each read from the vendor’s pricing page on the day of the run (docs-pricing-snapshot-2026-09-29.json). For claude-sonnet-5 the page’s footnote reads The previously scheduled increase to $3/$15 per million input/output tokens on September 1, 2026 will not occur. The rows are this run’s only; the product’s registry does not carry them. The runner’s registry, config/models.json, prices claude-sonnet-5 at 3 and 15, and each receipt’s pricing_snapshot.source names that file, config/models.json, although its prices are this run’s copy. Prices change the estimated cost below and no score.
  • A larger call cap across the run. A guard in front of Claude Code allowed 360 calls per run, where Report 011’s allowed 240: nine skill runs where Report 011 ran six. Per skill run the runner’s own cap stands at 80 calls. The guard also stops a run when a call reports any model other than the one it asked for; no run stopped.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.surface.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.surface.json; docs/reports/011/evidence/run-20260923T062806Z--run-record.json; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.surface.json; docs/reports/013/evidence/run-1/run-record.json; docs/reports/013/evidence/docs-pricing-snapshot-2026-09-29.json; config/models.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/guard.py; docs/reports/011/evidence/guard.py; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.stdout.txt.

What stayed fixed

The inputs are Reports 009 and 011’s. The same SKILL.md bytes (skill.content_hash, the same in all of this report’s receipts and Report 011’s for each skill: code-review-and-quality 13d360d7f786, git-workflow-and-versioning 91c8c72654ee, documentation-and-adrs b67a9f07ed10) and the same suites (suite.suite_hash: code-review-and-quality 5d729f885294, git-workflow-and-versioning 4e74150753d0, documentation-and-adrs 6cce54e7d9d0).

The runner is theirs. Driftproof runner 0.10.1 on the claude-cli surface, with the flags their runs used: at most 80 calls and 8.00 dollars of estimated spend per skill run. It puts the SKILL.md text in the prompt for the with-skill arm and gives the baseline arm the task alone, with no tools in either. It draws generations per arm until the spread settles or a maximum is reached, and the judge scores each draw against the case’s rubric on a continuous 0 to 1 scale.

The judge is theirs. claude-opus-5, with the grading template 82586d1e44f8 in every receipt.

The rule. A case’s band is its mean across draws plus or minus the sample standard deviation across draws: a descriptive spread with no coverage probability. Two with-skill bands separate under the rule when they do not overlap and their means differ by at least the 0.05 effect floor. A case that does not separate is read under spec 035’s rule: when the two arms’ spreads and draws could not have resolved a shift of the floor’s size, it reads not enough draws to conclude at this effect floor, and otherwise no separation detected. Neither is evidence that nothing differs. The verdicts are the runner’s: driftproof diff over each pair, whose outputs are published below.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/011/evidence/git-workflow-and-versioning-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.stdout.txt; config.js.

The figures behind each comparison: every run’s averages, spreads and answers

Claude Sonnet 5.5 against Claude Sonnet 5, every run

taskrunClaude Sonnet 5, with the skill: average ± spread (answers)Claude Sonnet 5.5, with the skill: average ± spread (answers)gap with the skillresultwhat the skill added (Claude Sonnet 5; Claude Sonnet 5.5)
code-review-and-qualityrun 10.880 ± 0.006 (3 answers)0.887 ± 0.025 (3 answers)+0.007too few answers to tell+0.302; +0.009
code-review-and-qualityrun 20.881 ± 0.005 (3 answers)0.900 ± 0.012 (3 answers)+0.019no clear difference+0.207; +0.051
code-review-and-qualityrun 30.657 ± 0.257 (4 answers)0.896 ± 0.002 (3 answers)+0.238too few answers to tell+0.085; +0.034
code-review-and-qualitythe three runs0.657 to 0.8810.887 to 0.900no clear difference in one of three; too few answers to tell in two of three+0.085 to +0.302; +0.009 to +0.051
git-workflow-and-versioningrun 10.814 ± 0.028 (3 answers)0.860 ± 0.009 (3 answers)+0.046too few answers to tell+0.012; +0.000
git-workflow-and-versioningrun 20.851 ± 0.002 (3 answers)0.863 ± 0.000 (3 answers)+0.012no clear difference+0.020; +0.013
git-workflow-and-versioningrun 30.831 ± 0.010 (3 answers)0.863 ± 0.009 (3 answers)+0.032no clear difference-0.004; +0.007
git-workflow-and-versioningthe three runs0.814 to 0.8510.860 to 0.863no clear difference in two of three; too few answers to tell in one of three-0.004 to +0.020; +0.000 to +0.013
documentation-and-adrsrun 10.602 ± 0.004 (3 answers)0.781 ± 0.141 (6 answers)+0.178clearly higher-0.059; +0.208
documentation-and-adrsrun 20.700 ± 0.098 (5 answers)0.813 ± 0.094 (7 answers)+0.113too few answers to tell-0.006; +0.238
documentation-and-adrsrun 30.641 ± 0.167 (5 answers)0.847 ± 0.015 (3 answers)+0.205clearly higher-0.085; +0.272
documentation-and-adrsthe three runs0.602 to 0.7000.781 to 0.847clearly higher in two of three; too few answers to tell in one of three-0.085 to -0.006; +0.208 to +0.272

The gap with the skill is the second average minus the first, in the same run. The result compares the two with-skill spreads, as the key under the first table says; the gap and what the skill added are shown beside it and decide nothing. What the skill added is a model’s average with the skill minus its average without it. The row for the three runs gives the lowest and highest figures across the runs, and counts the results.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--upgrade--run-3--documentation-and-adrs.md.

Claude Sonnet 5.5 against Claude Opus 5.5, every run

taskrunClaude Opus 5.5, with the skill: average ± spread (answers)Claude Sonnet 5.5, with the skill: average ± spread (answers)gap with the skillresultwhat the skill added (Claude Opus 5.5; Claude Sonnet 5.5)
code-review-and-qualityrun 10.907 ± 0.015 (3 answers)0.887 ± 0.025 (3 answers)-0.020too few answers to tell+0.076; +0.009
code-review-and-qualityrun 20.894 ± 0.017 (3 answers)0.900 ± 0.012 (3 answers)+0.006too few answers to tell+0.038; +0.051
code-review-and-qualityrun 30.903 ± 0.015 (3 answers)0.896 ± 0.002 (3 answers)-0.008no clear difference+0.190; +0.034
code-review-and-qualitythe three runs0.894 to 0.9070.887 to 0.900no clear difference in one of three; too few answers to tell in two of three+0.038 to +0.190; +0.009 to +0.051
git-workflow-and-versioningrun 10.861 ± 0.005 (3 answers)0.860 ± 0.009 (3 answers)-0.001no clear difference+0.353; +0.000
git-workflow-and-versioningrun 20.857 ± 0.000 (3 answers)0.863 ± 0.000 (3 answers)+0.007no clear difference+0.371; +0.013
git-workflow-and-versioningrun 30.856 ± 0.010 (3 answers)0.863 ± 0.009 (3 answers)+0.008no clear difference+0.276; +0.007
git-workflow-and-versioningthe three runs0.856 to 0.8610.860 to 0.863no clear difference in three of three+0.276 to +0.371; +0.000 to +0.013
documentation-and-adrsrun 10.650 ± 0.102 (6 answers)0.781 ± 0.141 (6 answers)+0.131too few answers to tell+0.116; +0.208
documentation-and-adrsrun 20.850 ± 0.007 (3 answers)0.813 ± 0.094 (7 answers)-0.037too few answers to tell+0.300; +0.238
documentation-and-adrsrun 30.840 ± 0.020 (3 answers)0.847 ± 0.015 (3 answers)+0.007too few answers to tell+0.322; +0.272
documentation-and-adrsthe three runs0.650 to 0.8500.781 to 0.847too few answers to tell in three of three+0.116 to +0.322; +0.208 to +0.272

The same columns, with Claude Opus 5.5 first. The result compares the with-skill scores only; what the skill added to each model is shown beside it and decides nothing. The vendor’s list prices for the two models are under what differs. No vendor statement about these two models is committed with this report, so none is quoted, and nothing on this page tests one.

Read from: docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--code-review-and-quality.md; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--git-workflow-and-versioning.md; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/diff--peer--run-3--documentation-and-adrs.md.

Claude Opus 5.5 against Report 011, every run

taskrunReport 011, with the skill: average ± spread (answers)this report, with the skill: average ± spread (answers)gap with the skillresultwhat the skill added (Report 011; this report)
code-review-and-qualityrun 10.910 ± 0.015 (3 answers)0.907 ± 0.015 (3 answers)-0.003too few answers to tell+0.230; +0.076
code-review-and-qualityrun 20.910 ± 0.015 (3 answers)0.894 ± 0.017 (3 answers)-0.016too few answers to tell+0.230; +0.038
code-review-and-qualityrun 30.910 ± 0.015 (3 answers)0.903 ± 0.015 (3 answers)-0.007too few answers to tell+0.230; +0.190
code-review-and-qualitythe three runs0.910 (one run)0.894 to 0.907too few answers to tell in three of three+0.230; +0.038 to +0.190
git-workflow-and-versioningrun 10.838 ± 0.027 (3 answers)0.861 ± 0.005 (3 answers)+0.023too few answers to tell+0.538; +0.353
git-workflow-and-versioningrun 20.838 ± 0.027 (3 answers)0.857 ± 0.000 (3 answers)+0.019too few answers to tell+0.538; +0.371
git-workflow-and-versioningrun 30.838 ± 0.027 (3 answers)0.856 ± 0.010 (3 answers)+0.018too few answers to tell+0.538; +0.276
git-workflow-and-versioningthe three runs0.838 (one run)0.856 to 0.861too few answers to tell in three of three+0.538; +0.276 to +0.371
documentation-and-adrsrun 10.661 ± 0.148 (6 answers)0.650 ± 0.102 (6 answers)-0.011too few answers to tell+0.094; +0.116
documentation-and-adrsrun 20.661 ± 0.148 (6 answers)0.850 ± 0.007 (3 answers)+0.189clearly higher+0.094; +0.300
documentation-and-adrsrun 30.661 ± 0.148 (6 answers)0.840 ± 0.020 (3 answers)+0.179clearly higher+0.094; +0.322
documentation-and-adrsthe three runs0.661 (one run)0.650 to 0.850clearly higher in two of three; too few answers to tell in one of three+0.094; +0.116 to +0.322

The same columns, with Report 011’s receipt first. Report 011 ran once, so its side of each row is the same receipt in all three runs. Report 011’s receipts are published with that report and linked here, not copied.

Read from: docs/reports/011/evidence/code-review-and-quality-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-1--code-review-and-quality.md; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-2--code-review-and-quality.md; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-3--code-review-and-quality.md; docs/reports/011/evidence/git-workflow-and-versioning-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-1--git-workflow-and-versioning.md; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-2--git-workflow-and-versioning.md; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-3--git-workflow-and-versioning.md; docs/reports/011/evidence/documentation-and-adrs-claude-opus-5-5-2026-09-23.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-1--documentation-and-adrs.md; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-2--documentation-and-adrs.md; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/diff--harness--run-3--documentation-and-adrs.md.

The run record: calls, costs and integrity

Run record

The runs. Each run went arm by arm, claude-sonnet-5-5 first, then claude-sonnet-5, then claude-opus-5-5, one skill at a time, code-review-and-quality first in each. The command file writes a status line after each skill run. The three runs went one after another with the same script and settings. Their log records that the script driving the second and third stopped after the second, in its words three-runs.sh died waiting on the quiet marker, run 3 not started, and that the third then ran, run 3 exit 0. Each receipt’s run.date_utc is written by the runner and is not read here as a start or a finish.

  • run 1, 20260929T035323Z: nine status lines, each with exit status 0 and one receipt, the last at 2026-09-29T04:37:54Z; 272 calls; 0 unmeasured draws.
  • run 2, 20260929T043803Z: nine status lines, each with exit status 0 and one receipt, the last at 2026-09-29T05:20:21Z; 272 calls; 0 unmeasured draws.
  • run 3, 20260929T053800Z: nine status lines, each with exit status 0 and one receipt, the last at 2026-09-29T06:24:35Z; 272 calls; 0 unmeasured draws.

The caps. A guard in front of Claude Code allowed 360 calls per run and 240 seconds per call.

The cost. Metered spend, as the runner reports it, was 0.00 dollars in each skill run’s console output: the claude-cli surface runs on a subscription. The estimated API-equivalent below is every draw’s generation and judge token counts, as each receipt records them, at the prices each receipt froze, with cached input counted at the full input price, as the runner counts it.

runarmcallsgeneration, estimated USDjudge, estimated USDtotal, estimated USD
run 1claude-sonnet-5-5840.795.596.38
run 1claude-sonnet-5800.965.316.27
run 1claude-opus-5-51082.087.249.32
run 2claude-sonnet-5-5880.835.786.62
run 2claude-sonnet-5881.065.636.70
run 2claude-opus-5-5961.786.318.09
run 3claude-sonnet-5-5720.684.805.48
run 3claude-sonnet-51041.286.888.16
run 3claude-opus-5-5961.886.588.46
all three runs11.3554.1465.48

Integrity. Each receipt validates with its receipt hash verified, and each sidecar names its receipt’s hash. The raw call records carry the SKILL.md text and stay unpublished; each run’s list of their sha256 is published.

Read from: docs/reports/013/evidence/runs-log.txt; docs/reports/013/evidence/run-1/run-record.json; docs/reports/013/evidence/run-1/status.jsonl; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/run-record.json; docs/reports/013/evidence/run-2/status.jsonl; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/run-record.json; docs/reports/013/evidence/run-3/status.jsonl; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.json; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.json; docs/reports/013/evidence/guard.py; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/code-review-and-quality-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/code-review-and-quality-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/documentation-and-adrs-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/code-review-and-quality-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/code-review-and-quality-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-2/documentation-and-adrs-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/code-review-and-quality-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-sonnet-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/code-review-and-quality-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/git-workflow-and-versioning-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-3/documentation-and-adrs-claude-opus-5-5-2026-09-29.stdout.txt; docs/reports/013/evidence/run-1/driftproof-calls.SHA256SUMS; docs/reports/013/evidence/run-2/driftproof-calls.SHA256SUMS; docs/reports/013/evidence/run-3/driftproof-calls.SHA256SUMS.

Published evidence

The files this report makes public. For each run, the nine receipts with their summaries, surface sidecars and the runner’s console output, the run record, its registry copy, the status lines and the sha256 of every raw call record; the twenty-seven driftproof diff outputs the verdicts are read from; the log of the three runs; the pricing snapshot; and the call guard. The pricing snapshot records the sha256 of the page it was read from; that page is not published. Each sidecar’s surface_note path is relative to the operator’s run directory; the run record it names is run-<k>/run-record.json here.

Report 011’s three Claude Opus 5.5 receipts, the other side of the harness check, are published with that report: code-review-and-quality, git-workflow-and-versioning, documentation-and-adrs. Validate a receipt with npx driftproof validate <file>. Each copy here is byte-identical to its twin under specs/121-report-013-sonnet-5-5/, and each sidecar names the receipt it belongs to and that receipt’s hash.

Receipts

Every receipt this report rests on, each one resolvable. Nine for each run, one per model and skill, the same bytes as the evidence copies above.

Validate any of them with npx driftproof validate <file>, and reproduce a verdict with npx driftproof diff <first> <second> over two receipts of one run.

Skills measured: addyosmani/agent-skills: code-review-and-quality, documentation-and-adrs and git-workflow-and-versioning.

Every Driftproof result in one file: JSONL or CSV, and what a row is and is not.

Want a skill measured, or think a result is wrong? It's free: how to ask.

Words with a dotted line link to the glossary, where each is explained in plain words.