CodeRabbit is an AI code review tool. It can review your PRs on GitHub / MRs on GitLab
after you push. You can also hook it into Claude Code to get the review and fix up the
nits with your agent prior to opening the PR.
<h1>Install the CLI</h1>
<pre><code class="language-bash">curl -fsSL https://cli.coderabbit.ai/install.sh | sh
</code></pre>
Then authenticate:
<pre><code class="language-bash">coderabbit auth login
</code></pre>
This opens a browser. Log in with GitHub, copy the token, paste it in the
terminal. The token lasts 90 days.
Verify it worked:
<pre><code class="language-bash">coderabbit --version
</code></pre>
<h1>Install the Claude Code Plugin</h1>
From any terminal:
<pre><code class="language-bash">claude plugin install coderabbit
</code></pre>
Or from inside a Claude Code session:
<pre><code class="language-text">/plugin install coderabbit
</code></pre>
The plugin wraps the CLI and exposes review commands you can run directly in
your Claude Code session. It also lets you trigger a review with plain English,
which Claude Code routes to the plugin automatically.
<h1>The Workflow</h1>
With both the CLI and plugin installed, the loop before any PR looks like this:
<pre class="mermaid">
graph TD
 A[Make changes with Claude Code] --> B[Run coderabbit review]
 B --> C{Issues?}
 C -->|Yes| D[Ask Claude Code to fix them]
 D --> A
 C -->|No| E[Create PR]
</pre>
Inside a Claude Code session, after you've made changes:
<pre><code class="language-text">/coderabbit:review uncommitted
</code></pre>
This reviews everything not yet committed. You can also review committed-but-
not-pushed changes:
<pre><code class="language-text">/coderabbit:review committed
</code></pre>
Or compare against a specific branch:
<pre><code class="language-text">/coderabbit:review --base main
</code></pre>
The review comes back as inline comments. You can ask Claude Code to fix specific
issues, re-run the review, and iterate until it's clean. Then push and open the
PR knowing CodeRabbit's automated review will be quiet.
It's kind of slow, but so is the PR review.
<h1>CLAUDE.md integration</h1>
CodeRabbit reads your <code>CLAUDE.md</code> files automatically. It treats them as code
guidelines and applies them during review.
That means that because my <code>CLAUDE.md</code> says "no em-dashes" and "never commit directly to
main", CodeRabbit enforces those same rules when it reviews your PR. You don't need to
configure anything extra.
<h1>Config with <code>.coderabbit.yaml</code></h1>
<code>.coderabbit.yaml</code> at the root gives control over what gets reviewed, how aggressively,
and with what focus per directory.
Notably:
<ul>
<li><code>path_filters</code>: glob patterns for files to skip entirely (lock files, build
artifacts, node_modules, etc)</li>
<li><code>path_instructions</code>: per-path AI instructions</li>
</ul>
Don't put <code>CLAUDE.md</code> in <code>path_instructions</code>. That makes CodeRabbit try
to review the file rather than use it as guidelines. The auto-detection handles
it correctly without any config.
<h2>Setup for this repo</h2>
Here's <a href="https://github.com/kylep/multi/blob/main/.coderabbit.yaml">the <code>.coderabbit.yaml</code> for this repo</a>.
<code>profile: chill</code> is the most significant setting. CodeRabbit's default
profile generates a lot of comments. I'm actually on the fence still about this though,
once I can get the AI agents to run the code review and fix up in a ralf-style-loop I
may go back to aggressive.
<code>poem: false</code> turns off CodeRabbit's cute poems, I'm not reading them like this.
Path filters drop lock files, build artifacts, and generated directories.
There's no value in reviewing a <code>package-lock.json</code> diff.
<code>infra/</code> and <code>apps/kytrade/</code> get security-focused instructions with
everything else deprioritized. Terraform style is not worth a comment.
A misconfigured IAM policy is.
<code>apps/blog/blog/markdown/posts/</code> gets a specific instruction to ignore
grammar, phrasing, and tone entirely. I'm specifically spending effort to not write
like a robot, I can't stand the writing style. CodeRabbit shouldn't fight it.
<code>samples/</code> is tutorial code I used to save examples of projects along the way.
<code>**/tests/**</code> is told to focus on whether tests actually assert something,
not on style. A test that always passes is a real problem. Variable naming is
not.

Kyle Pericak

"It works in my environment"

Categories

Tags