Agent skill · marketing growth · jeremylongshore
coderabbit-ci-integration
Design a fail-closed merge policy that combines CodeRabbit review state with provider checks without inventing a CodeRabbit status-check name. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "gate merges with CodeRabbit".
Why this skill is useful
Adds specific GitHub Actions workflows and configurations for integrating CodeRabbit as a CI gate that the AI wouldn't reliably generate on its own.
What it needs
Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit CI Integration Overview Build a merge policy from observable provider state. CodeRabbit review state, GitHub Checks ingestion, and branch protection are separate contracts. 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 reviews.requestchangesworkflow controls whether CodeRabbit can submit a changes-requested review. The GitHub Checks tool reads existing CI results; it does not prove CodeRabbit publishes a stable check name. Branch rules must use check names observed in the target repository. Emergency paths must retain independent tests, security checks, and audit evidence. 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. Inspect current branch rules, recent CodeRabbit reviews, and actual check-run names. 2. Choose whether review state is advisory or required, and list independent CI authorities. 3. Pilot the smallest YAML and branch-rule change without enabling enforcement. 4. Prove clean, failing, and rollback paths before enabling the policy. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-ci-integration--c30eca