Claude Code v2.1.223 · 5 Aug 2026
Cloud review failure message points at plain /code-review
A failed cloud review now points you at /code-review instead of a wrong command name.
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
0 Signal: worth watching, 1 to 5
Code Review Area: what it touches
Improvements Kind: in v2.1.223, 05 Aug 26
Improvements Section of the release
What
The fallback suggested when a cloud review fails now names the correct command.
Details
Previously the notification said to "use /review for a local review instead". It now reads "or use plain /code-review for a local review instead." Evidence
or use plain /code-review for a local review instead.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree Changed /review to be an alias of /code-review, which reviews the current diff or a PR (/code-review <level> <pr#>); use /code-review ultra…
See this entry in the whole of v2.1.223 →
5 Aug 2026 · 201 entries, this one is #106.
Use it now26 You'll notice99 Nothing to try yet21 Under the hood55
Open the release →
Names in this entry
slash /code-review Skill . Review the current diff, or a PR number, branch, or path you pass, for correctness bugs. Depending on your model and effort level, the review also covers cleanup opportunities. Pass --fix to apply findings, --comment to post them on the GitHub PR or GitLab merge request, or ultra to run a deep cloud review . Posting to a GitLab merge request requires Claude Code v2.1.257 or later. With ultra on a github.com PR target, pass --post to preselect posting the finished findings to the PR in the launch dialog; --post requires Claude Code v2.1.227 or later. See Review a diff locally for the effort levels, targeting, and how it relates to /simplify. Alias: /review
slash /review Alias of /code-review : reviews the current diff, or a PR number, branch, or path you pass, such as /review 1234, and takes the same effort levels and flags. With no level given, the review reuses the last low through max level you typed; see Review a diff locally for the exact rules. For a deep cloud review, use /code-review ultra . Before v2.1.223, /review was a separate command that ran a single-pass, read-only review of a GitHub pull request by number, listing open PRs to pick from when run with no argument; from v2.1.186 through v2.1.201, it ran the same multi-agent engine as /code-review medium
Anthropic's notes
Upstream's own release notes for v2.1.223 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Changed /review to be an alias of /code-review , which reviews the current diff or a PR (/code-review <level> <pr#>); use /code-review ultra for a deep cloud review
Changed /code-review with no effort level to reuse the level you typed last; type a level like /code-review high to change it
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 105 of 201
MCP control tool gives a session-specific message when controls are unavailable
You'll notice MCP
In v2.1.223 Improvements release-page order
Next → · 107 of 201
Ajv is loaded lazily for JSON-schema validation
You'll notice Elsewhere