Agent skill · operations · jeremylongshore
coderabbit-incident-runbook
Coordinate a review outage, harmful-output wave, access incident, or merge-policy failure without silently bypassing safeguards. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "handle a CodeRabbit incident".
Why this skill is useful
Adds specific executable scripts and procedures for handling CodeRabbit incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, gh installed locally. Requires coderabbit account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Incident Runbook Overview Contain impact while preserving independent security and CI. Separate provider health, service health, config, permissions, limits, and harmful output. 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 CodeRabbit can fail independently from repository CI. Limits and exclusions can resemble an outage. Bypass authority belongs to repository governance. Status evidence needs timestamps and local corroboration. 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. Declare scope, severity, owner, repositories, and exposure risk. 2. Freeze risky rollout changes and preserve independent controls. 3. Classify using health, installation, eligibility, config, limit, and provider evidence. 4. Restore, use an approved manual-review continuity path, or remain fail-closed. 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-incident-runbook--51e2bf