CodeRabbit Client Repository Onboarding (Onboarding)

CodeRabbit Client Repository Onboarding (Onboarding)

1. 01

   Confirm the client repo runs an active pull-request workflow on GitHub or GitLab

   CodeRabbit needs a repository connection and PR events to function, so audit the client's merge cadence and AI-generated code volume before quoting a managed engagement. A repo with fewer than roughly 10 PRs a month will not justify the retainer.

2. 02

   Install the CodeRabbit app on the client's GitHub or GitLab organization and scope it to the agreed repositories

   Limit the install to the repos named in the statement of work. Broad org-wide installs create review noise on internal tooling and inflate per-user seat counts.

3. 03

   Set the review style to Quiet, Chill, or Assertive to match the client's team conventions

   Quiet suits teams that already have a senior reviewer and only want blocking issues flagged. Assertive suits shops shipping high volumes of AI-assisted changes with no dedicated reviewer. Record the choice in the client runbook so a second delivery engineer can reproduce it.

4. 04

   Load the client's coding guidelines into the custom review rules

   CodeRabbit learns team conventions from feedback, but seeding the guidelines up front cuts the false-positive ramp. Pull the rules from the client's existing style guide or linter config rather than writing them from scratch.

5. 05

   Enable per-PR automated reviews and the prioritized Kanban queue

   The queue ranks PRs on business value and risk, which is the feature clients actually feel in week one. Turn on pre-merge checks and slop detection at the same time so AI-generated diffs get caught before a human opens them.

6. 06

   Route CodeRabbit alerts into the client's Slack workspace with channel routing

   Send blocking findings to the engineering channel and security findings to a separate channel. Mixed routing trains the client to ignore alerts, which kills the retainer at renewal.

7. 07

   Run the first 10 pull requests through the full review cycle and log every false positive

   Feed each false positive back through the agent's feedback mechanism. This is the tuning window that determines whether the client sees value in month one or churns.

8. 08

   Hand off the documented PR queue management SOP and confirm the seat count against the plan tier

   Essentials runs $30/mo per user monthly or $24/mo annual; Team runs $60/mo monthly or $48/mo annual. Reconcile the client's active reviewer count against the tier before the first invoice so the retainer margin holds.