What
- When the current branch's only commit is the repo's very first commit, ultrareview no longer silently falls back to diffing against an empty tree; it can offer to review every file in that first commit, but only after confirmation.
- Confirmation is skipped when the launch comes from certain internal request paths (flagged
confirmsBeforeLaunch), or when a person invoked the review command directly. - Review-scope messaging gained a dedicated "first commit" case, with a companion error message explaining that a fresh repo needs at least one commit before review can work, instead of falling through to a generic "no merge base" message.
- The remote-review precondition check's error message now says the argument can be a commit as well as a branch name, and a new bundling helper accepts a first-commit-only flag with a matching
first_committelemetry field recorded when a diff is too large to review.
Why
Previously, reviewing a brand-new repo with only its initial commit either failed or produced a confusing empty-diff review. Now Claude Code recognizes this case, explains it clearly, and can review the whole first commit with proper confirmation.
Names in the bundle/ultrareview/code-review ultra
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 since
A small documentation edit on Code Review touched a line naming /code-review ultra after this was published.
Ultrareview requires authentication with a claude.ai account and is not available on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry, or to organizations with Zero Data Retention enabled or with the [HIPAA configuration…code-review see the edit
Added since
A small documentation edit on Code Review touched a line naming /ultrareview after this was published.
To run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout.code-review see the edit
Confirmed since
Anthropic's documentation has since written up /ultrareview, on Commands.
| `/code-review [low\|medium\|high\|xhigh\|max\|ultra] [--fix] [--comment] [pr#\|branch\|path]` | **[Skill](/docs/en/skills#bundled-skills).** Review the current diff, or a PR number, branch, or path you pass, for correctness bugs. Dependi…commands see the edit
Confirmed since
Anthropic's documentation has since written up /code-review ultra, 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…commands see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /code-review ultra, on Commands.
Anthropic's release notes agree
Improved /ultrareview when there's nothing to review: messages say which case you're in, offer a command that reviews your latest commit…