Skip to content
← Back to release · 2.1.277
Improvements / v2.1.277

Clarify /ultrareview with nothing to review

CHANGELOG · original

Improved /ultrareview when there's nothing to review: messages say which case you're in, offer a command that reviews your latest commit, and a new repository's first commit is reviewed in full
Open official changelog ↗

Documentation

Documentation excerpt

Diff limits and fallbacks

Ultrareview checks the diff before any review work runs and tells you when it can't review it as-is:

  • Diff too large: a branch review can include up to 500 changed files and 8,000 changed lines by default. The exact values can change, and the refusal names the ones in effect, the size of your diff, and the files with the most changed lines. Claude Code refuses a too-large pull request the same way, naming its file and line counts but not the per-file breakdown

  • Nothing to review: when the diff against the base is empty, ultrareview refuses and names the branch or commit it compared against and the case you're in, such as being on the base branch itself with nothing uncommitted, or a branch whose commits are all part of the base already. It also suggests the way out for that case, such as switching to the branch with your work, staging or committing local edits, or passing a different base

  • First commit: a repository's first commit has nothing earlier to compare with, so ultrareview reviews every file in it after you confirm in the launch dialog. If you have untracked files, it refuses instead and tells you to git add the ones you want reviewed. The same size limits apply.

    A first commit is reviewed whole only after that confirmation, so the claude ultrareview subcommand and claude -p refuse it and point you to an interactive session instead. Requires Claude Code v2.1.277 or later

  • No merge base: when your branch shares no history with the base branch, or the repository has no base branch to compare with, ultrareview reviews every tracked file in the repository instead. The fallback requires a full clone and applies the same size limits. It launches only when you confirm in the launch dialog or run the claude ultrareview subcommand yourself. In claude -p and anywhere else neither happens, ultrareview refuses, says the review would cover every file, and points you to an interactive session.

    On a checkout with no branches or other refs, such as a detached HEAD created by checking out FETCH_HEAD after fetching a URL, Claude Code refuses the review and suggests creating a branch first

Documentation snapshot · 2026-09-23

Change details