CodeRabbit Commands: Every @coderabbitai Command (2026)

The command table

Every command is a pull request comment starting with @coderabbitai. This is the whole reference.

Command	What it does	When you want it
@coderabbitai review	Incremental review of what changed since last time	Automatic reviews are off, or you want a re-check after a push
@coderabbitai full review	Re-reviews every file from scratch	After a rebase, force push, or large refactor
@coderabbitai pause	Stops reviews on this PR	Mid-iteration, when you do not want a review per commit
@coderabbitai resume	Restarts reviews	You are ready for feedback again
@coderabbitai resolve	Marks all CodeRabbit comments resolved	You have addressed the feedback your own way
@coderabbitai summary	Regenerates the PR summary	The description drifted after you changed scope
@coderabbitai configuration	Prints the active config for the repo	Debugging why it is behaving unexpectedly
@coderabbitai help	Lists commands	You forgot one

Two that are not comments:

• @coderabbitai ignore goes in the pull request description. While that text is present, CodeRabbit will not auto-review any commit on the PR. You can still trigger a manual review with the commands above.
• @coderabbitai in the pull request title makes CodeRabbit generate the title for you.

If your organisation runs the bot under a different service-account handle, substitute it. The keywords do not change.

The three commands that actually matter

Most of that table is situational. Three of them change how you work.

pause is the one people should use and do not

The default behaviour reviews every push. If you are iterating - push, fix, push, fix - you get a review per commit, which is where “CodeRabbit is too noisy” usually comes from. It is not the reviewer being verbose, it is you asking it eight times.

Comment @coderabbitai pause when you start iterating. Comment @coderabbitai resume when the branch is actually ready. You get one good review instead of eight partial ones, and the PR thread stays readable.

This is also the fix for the rate limit on the free tier, where each of those eight reviews counts against your hourly allowance. We covered that in is CodeRabbit free for open source.

full review after any history rewrite

Incremental review works from what changed since the last pass. Rebase, squash, or force push and that history no longer describes reality, so the incremental diff can be nonsense - reviewing changes that no longer exist or skipping ones that do.

Any time you rewrite history, @coderabbitai full review. It is the difference between a review of your branch and a review of a branch that used to exist.

resolve to close out a thread honestly

You will often fix a flagged issue differently from how it was suggested. Clicking resolve on fifteen individual comments is tedious enough that people just leave them open, and an open thread on a merged PR is noise for whoever reads it next.

@coderabbitai resolve clears them in one action.

Chatting with the bot

The commands are the deterministic surface. Underneath it, CodeRabbit is conversational, and this is the underused half of the product.

Reply to a review comment to continue that specific thread:

I pushed a fix in commit a1b2c3d, please review it.

Tag it inline on the Files changed tab to ask about a specific location:

@coderabbitai generate unit testing code for this file.

Tag it in a PR comment to ask about the branch as a whole:

@coderabbitai read src/utils.ts and generate unit testing code

@coderabbitai help me debug my CodeRabbit configuration file

That last one is worth knowing about. When reviews are behaving oddly, you can ask the bot to explain its own configuration rather than reading the YAML schema yourself.

The constraint is the context window. Large, vague requests degrade noticeably. “Refactor this service” gets you a worse answer than three scoped questions. Prefer inline comments for anything file-specific, since they carry the location as context for free.

The workflow that works

Putting it together, the pattern that produces the least friction:

1. Open the PR as a draft if you are still iterating, or comment @coderabbitai pause immediately.
2. Iterate freely. No reviews, no noise, no rate limit consumption.
3. Comment @coderabbitai resume when the branch is genuinely ready.
4. Read the review. Reply inline to anything you disagree with rather than silently ignoring it - the reply is context for the next pass.
5. Push fixes, let the incremental review confirm them.
6. @coderabbitai resolve to clear anything you handled differently.
7. @coderabbitai full review if you rebased at any point before merging.

Teams that fight with AI reviewers are usually running step 2 with reviews switched on.

Making it permanent with configuration

Commands control one pull request. For behaviour you want every time, use a .coderabbit.yaml file at the repository root.

Two keys pair naturally with the commands above:

• ignored_branch - a comma-separated list of branches to skip, wildcards supported. Better than remembering @coderabbitai ignore on every dependabot PR.
• ignored_titles - snippets that, when matched in a PR title, suppress review. WIP and chore are the obvious entries.

Add the schema line at the top of the file and your editor’s YAML language server will autocomplete the rest:

# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

The full key reference is in our CodeRabbit configuration guide, and custom review instructions covers telling it what to care about in plain English.

Bottom line

The command surface is small and most of it you will use once. The three worth committing to memory are pause and resume around iteration, and full review after any rebase.

If CodeRabbit feels too chatty, try pausing during iteration before you go looking for a quieter tool. A large share of the volume people complain about is the reviewer being asked eight times rather than once. For the configuration-level fixes when that is not enough, see our CodeRabbit review for where it genuinely trades noise for coverage.

Further Reading

• CodeRabbit Too Noisy? How to Cut the Comments (2026)