Agent skill · software engineering · jeremylongshore
coderabbit-reference-architecture
Design a governed deployment across provider, configuration, review, knowledge, tools, data, identity, and observability. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "design CodeRabbit architecture".
Why this skill is useful
Adds a comprehensive .coderabbit.yaml configuration template and specific review instructions that enhance the AI's ability to set up code review processes.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. Authentication Treat Git-provider sessions, CodeRabbit web sessions, CLI credentials, and CodeRabbit API keys as separate credentials. Use only an already-approved session or secret-manager reference, never print a secret, and do not place credentials in .coderabbit.yaml, source files, logs, or deliverables. Instructions 1. Map organizations, providers, repos, trust zones, data, identities, plans, and gates. 2. Draw configuration resolution and review-event flows with ownership. 3. Select knowledge, tools, cache, retention, reporting, and continuity controls. 4. Validate happy, exclusion, provider-failure, secret, and rollback paths. Tool Discipline Use Glob to locate candidate configuration and evidence files without widening scope. Use Grep to find relevant fields, commands, identifiers, and stale claims. Use Read to inspect the smallest required files and authoritative evidence. Use Write only for a new approved local draft or evidence artifact. Use Edit only for a bounded approved change whose rollback is known. Do not use these file tools as a substitute for authenticated CodeRabbit or provider operations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-reference-architecture