Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Commands reference missing `/ultrareview` cloud code review command [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49291•Fetched 2026-04-17 08:45:25
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeekq2-kkendallq2-kkendall
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

Built-in commands table for review commands and PR review workflows

Current Documentation

The commands reference currently says:

/review | Deprecated. Install the code-review plugin instead: claude plugin install code-review@claude-plugins-official

/security-review | Analyze pending changes on the current branch for security vulnerabilities. Reviews the git diff and identifies risks like injection, auth issues, and data exposure

The Code Review page currently documents GitHub comment triggers instead of a CLI slash command:

Two comment commands start a review on demand. Both work regardless of the repository's configured trigger, so you can use them to opt specific PRs into review in Manual mode or to get an immediate re-review in other modes.

@claude review — Starts a review and subscribes the PR to push-triggered reviews going forward

@claude review once — Starts a single review without subscribing the PR to future pushes

No documentation currently exists for /ultrareview, its cloud execution model, or its argument behavior.

What's Wrong or Missing?

Changelog v2.1.111 added /ultrareview for running comprehensive code review in the cloud using parallel multi-agent analysis and critique, with two documented invocation modes: no arguments to review the current branch, or /ultrareview <PR#> to fetch and review a specific GitHub PR.

The current docs do not mention this command anywhere in the command reference or review docs. Users reading the docs still see a deprecated /review command and GitHub comment-based @claude review workflows, but nothing that explains:

  • that /ultrareview exists
  • that it runs review in the cloud
  • that it can review the current branch with no arguments
  • that it accepts a PR number to review a specific GitHub PR
  • how it relates to existing Code Review documentation

Suggested Improvement

Add /ultrareview [PR#] to the commands reference with a short description, requirements, and examples such as:

  • /ultrareview
  • /ultrareview 1234

Also add a short cross-reference in the Code Review docs that explains when to use /ultrareview versus repository-level Code Review and @claude review comments.

At minimum, document:

  • that the command runs a comprehensive review in the cloud
  • that it uses parallel multi-agent analysis/critique
  • the default current-branch behavior when no argument is provided
  • the PR-number form for reviewing a specific GitHub PR

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/commandsBuilt-in command reference currently lists deprecated /review and adjacent review commands, but not /ultrareview
https://code.claude.com/docs/en/code-reviewReview workflow page explains multi-agent PR reviews and @claude review / @claude review once, but not the new /ultrareview CLI entry point

Total scope: 2 pages affected

Source: Changelog v2.1.111

Changelog entry:

Added /ultrareview for running comprehensive code review in the cloud using parallel multi-agent analysis and critique — invoke with no arguments to review your current branch, or /ultrareview <PR#> to fetch and review a specific GitHub PR

extent analysis

TL;DR

Add documentation for the /ultrareview command to the commands reference and Code Review docs, including its cloud execution model, argument behavior, and relationship to existing Code Review documentation.

Guidance

  • Update the commands reference to include /ultrareview [PR#] with a short description, requirements, and examples.
  • Add a short cross-reference in the Code Review docs to explain when to use /ultrareview versus repository-level Code Review and @claude review comments.
  • Document the command's behavior, including its default current-branch behavior when no argument is provided and the PR-number form for reviewing a specific GitHub PR.
  • Ensure the documentation covers the command's cloud execution model and parallel multi-agent analysis/critique.

Example

An example of the updated commands reference could be:

/ultrareview [PR#] | Run a comprehensive code review in the cloud using parallel multi-agent analysis and critique. Invoke with no arguments to review the current branch, or specify a PR number to review a specific GitHub PR.

Notes

The documentation update should be applied to the two affected pages: https://code.claude.com/docs/en/commands and https://code.claude.com/docs/en/code-review.

Recommendation

Apply workaround: Update the documentation to include the missing information about the /ultrareview command, as this will provide users with the necessary information to understand and use the feature correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING