How to Set Up CodeRabbit on a GitHub Repo in 20 Minutes
CodeRabbit is an AI code review bot that comments on your pull requests inside GitHub, GitLab and Bitbucket. Install it, open a PR, and within about two minutes you get line-level comments, a PR summary, and suggested patches you can commit with one click.
Setup takes one afternoon or twenty minutes, depending on how much you tune it. Do the tuning. An untuned reviewer on a busy repo produces 40 comments on a 200-line diff and your team mutes the bot by Friday.
What is CodeRabbit and what does it actually review?
CodeRabbit reads your full diff, the surrounding file context, and your repo’s configured linters, then posts structured feedback: a change summary, a walkthrough broken down by file, and inline suggestions.
It checks three different layers:
- Correctness — null handling, off-by-one, error paths that never fire
- Style and lint — issues ESLint or Ruff would catch, so it complements rather than replaces CI
- Patterns — duplicated logic, unused imports, secrets in code
It does not run your tests. It does not know your product requirements. Treat it as a second pair of eyes from a developer who read the diff once, not a gatekeeper.
How do I install CodeRabbit on a repo?
- Go to CodeRabbit’s dashboard and sign in with GitHub.
- Select “Add repositories” and choose the org.
- Grant access to one repo first. Not all of them. Trust comes later.
- Install the GitHub App on that repo. You need admin rights on the repo, not the org.
- Open a tiny test PR — one file, one real change. Check the bot comments within 3–5 minutes.
If nothing arrives, check two things: the app is granted access to that specific repo (GitHub org permissions can silently exclude it), and the PR isn’t a draft. Draft PRs are reviewed only if you enable it.
How do I configure .coderabbit.yaml so the bot stays quiet?
Add a .coderabbit.yaml at the repo root. This is the highest-leverage file in the whole setup.
language: en
reviews:
profile: chill
request_changes_workflow: false
high_level_summary: true
poem: false
auto_review:
enabled: true
drafts: false
base_branches: [main, develop]
path_filters:
- "!package-lock.json"
- "!dist/"
- "!migrations/"
path_instructions:
- path: "src/api/**"
instructions: "Flag any unhandled promise rejection and missing input validation."
The chill profile posts fewer, higher-signal comments. assertive is the default and is noisy. Set poem: false unless you enjoy the bot writing a rhyming summary of your hotfix — it’s a real feature and it gets old fast.
Path filters matter more than people expect. Generated code, lockfiles and migrations produce hundreds of false positives and teach your team to ignore the bot.
What does CodeRabbit cost and where does the free tier stop?
As of late 2026: Free for open-source repos and a limited number of private-repo PR reviews per month (enough for a solo developer, not for a team). Lite is around $12–15 per developer per month. Pro sits near $24 and adds heavier models, more review depth and IDE integration.
What the paid tiers actually buy you:
- Reviews on more than a handful of PRs
- Reviews on private repos without a monthly cap
- Longer diffs reviewed in one pass (large PRs get truncated on cheap plans)
For a team of five pushing 60 PRs a month, Lite is fine. Pay for Pro if you’re reviewing diff sizes above about 400 changed lines regularly.
Which repos should not use CodeRabbit?
Skip it where the diff is unreadable: repos with giant generated bundles, vendors, or data dumps. Also skip during a heavy refactor week — the bot will comment on every moved line and the noise hides real issues.
Quick Summary
- CodeRabbit reviews pull requests inside GitHub, GitLab and Bitbucket; setup is a single app install plus a YAML file.
- Use the
chillprofile, path filters, and the smallest possible repo scope on day one. - Keep
poem: falseand skip draft PRs to cut notification load. - Free tier covers OSS and light private use; Lite runs roughly $12–15 per dev per month.
- Not a test runner — combine it with CI, not instead of it.
