[DOCS] Ultrareview docs list only a bare PR number, not accepted PR reference formats

Status Fixed / completed
Reported on v2.1.212
Maintainer reply None cached
Activity 1 comment · opened Jul 17, 2026 · closed Aug 17, 2026

Documentation Type

Unclear/confusing documentation

Documentation Location

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

Section/Topic

“Run ultrareview from the CLI” and the pull-request argument examples.

Current Documentation

The guide currently says:

“To review a GitHub pull request instead, pass the PR number.”

The example is:

/code-review ultra 1234

What's Wrong or Missing?

Claude Code 2.1.212 accepts common PR references such as #123, PR 123, and a pasted PR URL. The current guide presents only a bare numeric argument and does not tell users that these other forms are supported or show their equivalent command syntax.

Users who naturally paste a PR URL or type the reference copied from GitHub cannot tell from the documentation whether the input is supported, and the guide makes the accepted input contract look narrower than it is.

Suggested Improvement

Replace the single PR-number example with a short table or examples showing the accepted forms:

/code-review ultra 1234
/code-review ultra #1234
/code-review ultra PR 1234
/code-review ultra https://github.com/owner/repo/pull/1234

State whether the same forms are accepted by the claude ultrareview subcommand and document any repository or host restrictions that apply to pasted URLs.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/ultrareview | Primary interactive and non-interactive usage examples |
| https://code.claude.com/docs/en/commands | /code-review ultra and /ultrareview command discovery |

Total scope: 2 pages should describe the same accepted PR-reference contract.

The additional input forms were fixed in Claude Code 2.1.212; the release notes are listed at https://code.claude.com/docs/en/changelog.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗