CodeRabbit Reference Architecture

Overview

Make authority and data flow explicit. Separate source, control planes, provider events, knowledge sources, and reporting.

Prerequisites

• Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner.
• Read references/official-docs.md and re-check any time-sensitive contract before execution.
• Use synthetic or read-only evidence until the approval boundary is satisfied.
• Preserve the repository's independent CI, security, and human-review requirements.

Current Contract

• Repository YAML, central config, settings, and global overrides form precedence.
• CodeRabbit can use guidelines, learnings, linked repos, MCP, and tools.
• Provider support and auth differ.
• Dashboards, exports, reports, and APIs are distinct.