Agent skill · software engineering · jeremylongshore
coderabbit-prod-checklist
Make an evidence-backed go-live decision for installation, configuration, governance, security, continuity, and operations. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "review CodeRabbit go-live".
Why this skill is useful
Adds a comprehensive executable script for validating CodeRabbit production readiness that includes configuration checks and review history verification.
What it needs
Requires gh, python3 installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Production Readiness Overview Turn a pilot into an explicit production decision. Each gate needs an owner, evidence, failure criterion, and rollback. 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 Configuration may resolve from multiple authorities. Provider permissions, roles, seats, and plans are distinct. Review state must coexist with independent CI and security. Retention, exports, keys, and support need owners. 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. Verify scope, ownership, permissions, config, plan, seats, roles, and data. 2. Exercise happy, skipped, invalid-config, limit, provider-failure, and rollback paths. 3. Confirm dashboards, incident ownership, continuity, and recertification. 4. Record GO, CONDITIONAL GO, or NO-GO with evidence. 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. Approval Boundaries Named repository, security, privacy, billing, and operations owners approve their own gates. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-prod-checklist