Skip to content
BENIBIX Learn

/code-review Command

Also known as /code-review, /review, /ultrareview, /code-review ultra

It checks your changes for bugs before you ship them.

Think of it like

It is like a friend who checks your work for mistakes.

Example

Lucy is about to open a pull request. She runs /code-review and goes on working. A few minutes later the review reports an off-by-one bug in her loop.

Why it matters

A bug found before the pull request costs less than one a teammate finds. It costs much less than one users find.

Definition

/code-review is a bundled skill that checks your changes for bugs. With no target, it reviews your branch's new commits and anything not yet committed. Name a pull request, a branch, a path or a range of commits to review that instead. It runs as a background subagent, so it does not fill your chat. An effort level from low to max trades sure findings for wider ones. --fix applies the findings, --comment posts them on the pull request, and ultra runs a deep review in the cloud.

Example code

console
/code-review high --fix
Review at high effort, then fix what it finds.
A low level reports fewer findings, but surer ones. A high one looks wider.

Common mistake

Expecting it to follow REVIEW.md. It follows your CLAUDE.md. REVIEW.md is read only by the Code Review service on GitHub.

Key takeaways

  1. 1
    Looks for bugs. In your changes.
  2. 2
    Low to max. Sure to wide.
  3. 3
    Fix or comment. --fix, --comment.

Compare

Learn it properly