You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
The help text for /review no longer unconditionally promises that it covers reuse, simplification, and efficiency cleanups alongside correctness bugs. It now says those cleanups are included only 'where the model's review recipe covers them.'
Why
This sets more accurate expectations: /review may not always surface reuse, simplification, or efficiency suggestions, depending on which review recipe is in use, whereas the previous wording implied it always would.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Week 32 · August 3–7, 2026 touched a line naming /review after this was published.<div><code>/review</code> is now an alias of <a href="/docs/en/code-review-local"><code>/code-review</code></a>, and <code>/code-review</code> with no effort level reuses the level you typed last</div>whats-new/2026-w32see the edit
Confirmed sinceAnthropic's documentation has since written up /review, on Commands.**Before you ship.** `/diff` shows what changed. `/code-review` checks the current diff for correctness bugs and can apply the findings with `--fix`; pass a PR number, such as `/code-review high 1234`, to review a pull request instead. `/r…commandssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /review, on Commands.