When a repository is too large for full-repo review, the suggestion now says "Push a PR and use /ultrareview <PR#> instead" (previously referenced /review ).
Evidence
Large repo message (search for "Repo is too large. Push a PR and use")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.86 →
Names in this entry
slash /ultrareview Run a deep, multi-agent code review in a cloud sandbox with ultrareview . Pass a PR reference to review that pull request, or a base branch or commit to change the comparison base. The preferred invocation is /code-review ultra, and /ultrareview is an alias. Includes 3 free runs on Pro and Max, then requires usage credits
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
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 · 13 of 19
Agent System Prompt Refinements
In v2.1.86 Changes release-page order
Next → · 15 of 19
Plugin Telemetry Overhaul