Claude Code just shipped /ultrareview. Here is the practitioner breakdown.

🔥

Anthropic dropped a new slash command called /ultrareview in Claude Code v2.1.111, and it quietly changes how I review my own code before I ship it. Here is what it does, when to use it, when to hold back, and the catch most people are glossing over.

What it actually is

/ultrareview runs a full code review in the cloud using parallel reviewer agents while you keep working locally.

- Type /ultrareview with no arguments. It reviews your current branch.

- Type /ultrareview 123. It pulls PR #123 from GitHub and reviews that.

By default it fires up 5 reviewer agents in parallel. Configurable up to 20. Each agent independently scans your diff for real bugs, and the command only surfaces a finding after it has been reproduced and verified. No "you might want to use const" noise. No lint-style nagging. Verified findings only.

When to pull the trigger

Spend a run when the cost of a missed bug is real:

- Payment code

- Auth changes

- Database migrations

- Large refactors touching many files

- Any pre-merge review on a business-critical branch

Do not burn a run on a one-line typo fix. The value lives in wide, high-stakes diffs where a human reviewer would take an hour and still miss something.

The catch

Users are reporting three free runs total on Pro and Max plans. Not three per month. Three, period. After that it meters against your plan.

Treat them like good steakhouse reservations. You do not book one to show up and order a side salad.

How I am using it

1. Finish a feature branch.

2. Run my own tests locally.

3. Fire /ultrareview before I open the PR.

4. Read the findings. Fix what matters. Push.

5. Only then ask a human to review.

It does not replace a human reviewer. It does catch the things your eyes stopped seeing three hours ago.

Try it

Update Claude Code to 2.1.113 or later. Inside a git repo with real changes, type /ultrareview. Watch the fleet spin up. Come back in a few minutes.