coderabbit-ci-integration

name	coderabbit-ci-integration
description	Configure CodeRabbit as a CI gate with GitHub Actions, branch protection, and review enforcement. Use when setting up CodeRabbit as a required check, gating merges on review approval, or integrating CodeRabbit status into your CI pipeline. Trigger with phrases like "coderabbit CI", "coderabbit GitHub Actions", "coderabbit required check", "coderabbit merge gate", "coderabbit CI pipeline".
allowed-tools	Read, Write, Edit, Bash(gh:*), Bash(git:*)
version	1.0.0
license	MIT
author	Jeremy Longshore <[e-mail]>
compatible-with	claude-code, codex, openclaw
tags	["saas","coderabbit","ci-cd","github-actions"]

CodeRabbit CI Integration

Overview

Integrate CodeRabbit into your CI/CD pipeline as a merge gate. CodeRabbit posts a GitHub Check on each PR, and you can require this check to pass before merging. This skill covers branch protection rules, GitHub Actions workflows that react to CodeRabbit reviews, and strategies for enforcing review quality in CI.

Prerequisites

• CodeRabbit GitHub App installed on your repository
• GitHub repository with branch protection enabled
• .coderabbit.yaml committed to repository root
• GitHub Actions enabled on the repository

Instructions

Step 1: Enable CodeRabbit as a Required Status Check

1. Go to GitHub repo > Settings > Branches > Branch protection rules
2. Click "Add rule" (or edit existing rule for `main`)
3. Enable "Require status checks to pass before merging"
4. Search for "coderabbitai" in the status checks list
5. Select it as a required check
6. Save changes

Result: PRs cannot be merged until CodeRabbit completes its review.

Step 2: Configure Review Approval Behavior

# .coderabbit.yaml - Control when CodeRabbit blocks merge
reviews:
  request_changes_workflow: true   # CodeRabbit marks review as "Changes Requested" for issues
  # When true: PRs with issues show as "Changes Requested" (blocks merge if reviews required)
  # When false: CodeRabbit only posts "Comment" reviews (never blocks merge)

  profile: "assertive"             # Controls comment volume
  # chill: fewer comments, only critical issues
  # assertive: balanced, blocks on significant issues
  # nitpicky: detailed comments, blocks more frequently

  auto_review:
    enabled: true
    drafts: false