Before you start
- Check which profile is in effect. Post
@coderabbitai configurationon a pull request and readreviews.profileand its# Source:comment. See Check which configuration a review used. - Decide where you change settings. For one repository, use the configuration file or Repository settings. For every repository, see Apply settings to every repository.
Lower the review profile
reviews.profile is the main volume control. It has three values.
- In the app
- YAML V2
- YAML V3
Open Review > Review settings, choose Organization defaults or a repository, open Reviews > General, and set the profile.
assertive switches CodeRabbitâs generated fallback tool configurations to stricter rule sets.
Exclude files that donât need review
Path filters remove files before CodeRabbit reviews them. Use exclusions only, so every other file stays in scope. An exclusion always wins. A single include pattern turns the list into an allowlist. The one exception restores a default exclusion: copy its exact pattern without the leading!. That turns off only that default. A broader pattern doesnât restore default-excluded files and creates an allowlist.
- YAML V2
- YAML V3
Tell CodeRabbit to skip style nits
Linters and formatting tools should own style. Add one path instruction that applies to every file and limits CodeRabbit to issues that matter.**/* matches every file, hidden files (names starting with a dot) included. An instruction only guides the model. The profile is the structural volume control, so use both. In V3, put the same text in a document in .coderabbit/instructions/. See Instruction and check documents.
Leave style to your own linters
Turn off a tool that duplicates a linter you already run, or point it at your own configuration file. Use the toolâs own config file for per-rule control. A profile change affects every tool. See Tools.Review fewer pushes
By default, CodeRabbit reviews every push as an incremental review and pauses after five reviewed commits. For active pull requests, lower the limit, as in this example:- YAML V2
- YAML V3
0 turns pausing off. The counter resets when a review resumes.
To stop automatic reviews of new pushes altogether, turn incremental review off instead: set reviews.auto_review.auto_incremental_review to false in V2, or reviews.auto_review.incremental_review to false in V3. To pause or resume a single pull request, comment @coderabbitai pause or @coderabbitai resume.
Trim the output
Each of these V2 keys removes a section of the walkthrough or summary:
Keep
reviews.collapse_walkthrough (V3 reviews.output.walkthrough.collapse) at true so the walkthrough stays collapsed. It hides the walkthrough but doesnât remove it.
tone_instructions (V2) or fun.tone_instructions (V3) changes how comments read, up to 250 characters. It isnât a volume control.
Check the result
Compare the next few pull requests against recent ones. Look at the number of inline comments, the collapsed sections in the summary, and whether the comments you still get are the ones you want. If a useful comment disappeared, raise the profile one step or narrow the instruction.Whatâs next
Write review instructions that work
Make the instructions you add specific, scoped and checkable.
Set review strictness, tone and language
Learn what the profile, tone and language settings change.
Teach CodeRabbit your review rules
Choose between path instructions, code guidelines and custom checks.