coderabbit-incident-runbook — Claude Code skill
coderabbit-incident-runbook — a skill that walks an operator through a CodeRabbit incident: a review outage, a burst of bad suggestions, lost access or a broken merge policy. It keeps the response ordered while the cause is still unclear.
MIT 1 installs ★ 2,935 updated 2026-10-29
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a claude-codeWhat coderabbit-incident-runbook does
The skill gives an operator a fixed order of work. Scope, severity, owner and affected repositories get written down first, then risky rollouts are frozen. Independent CI, security scans and human review are explicitly kept in force, so an incident never turns into a quiet bypass.
Next the cause gets sorted: provider health, installation, eligibility, config, limits. The toolset is narrow — Read, Glob and Grep for finding and reading evidence, while Write and Edit are reserved for approved local drafts. Those file tools do not stand in for work inside CodeRabbit or at the Git provider. What comes out is a timeline, impact, containment, recovery proof and follow-ups.
Live changes need current CodeRabbit documentation plus approved access to the organization, repository or billing. Until that approval exists, evidence stays synthetic or read-only. Git-provider sessions, web sessions, CLI credentials and API keys count as separate secrets, and none of them belong in .coderabbit.yaml, source files or logs. If the vendor contract is unclear or two sources disagree, changes stop and the owner resolves it.
What it helps with
- sort out a review outage while repo CI is still green
- stop a wave of harmful suggestions without switching off other checks
- restore organization access after a permissions incident
- build a timeline and recovery proof for the postmortem
- tell a plan limit apart from a real service failure
Example prompts for the agent
- Handle the CodeRabbit incident in
api-service: reviews stopped arriving this morning, gather evidence and propose a recovery path. - CodeRabbit is posting harmful suggestions in
web-app. Freeze the rollout and list what to check in config and permissions. - Work out whether
paymentsis hitting a limit or a genuine outage; read-only access only.
How to install coderabbit-incident-runbook
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a claude-code2Manually: put the files in place
~/.claude/skills/coderabbit-incident-runbook/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/coderabbit-incident-runbook/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a codex2Manually: put the files in place
.agents/skills/coderabbit-incident-runbook/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a cursor2Manually: put the files in place
.cursor/skills/coderabbit-incident-runbook/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/coderabbit-incident-runbook2Manually: put the files in place
.github/skills/coderabbit-incident-runbook/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/coderabbit-incident-runbookManually: put the files in place
.devin/skills/coderabbit-incident-runbook/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about coderabbit-incident-runbook
How do I install coderabbit-incident-runbook in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-incident-runbook -a claude-code. The skill then sits at ~/.claude/skills/coderabbit-incident-runbook/SKILL.md.
What does coderabbit-incident-runbook do?
It sets the order for a CodeRabbit failure: declare scope and owner, freeze risky changes, split the cause across provider health, installation, permissions, config and limits, then restore reviews or stay fail-closed.
What access is required before making live changes?
Approved access to the CodeRabbit organization, repository and billing, along with the vendor's current documentation. Without that approval the skill collects synthetic or read-only evidence only.
Source text
SKILL.md · MIT
--- name: coderabbit-incident-runbook description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit version: 2.0.0 argument-hint: "[target] [evidence-or-scope]" model: inherit effort: high author: Jeremy Longshore <[email protected]> license: MIT compatibility: Requires current CodeRabbit documentation and approved access for any live organization, repository, billing, or API change tags: [saas, coderabbit, incident-response, continuity, rollback] --- # 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. ## Approval Boundaries Only documented repository authority may relax a CodeRabbit-related gate; unrelated controls remain required. Keep analysis and drafts local until approval is explicit, and record who approved the action and its scope. ## Output A timeline, impact, containment, continuity control, recovery proof, and follow-up actions. Include source dates, unknowns, and the exact boundary between observed fact and recommendation. ## Error Handling | Condition | Response | |---|---| | Current contract is unclear or docs disagree | Stop mutation, cite both sources, and request owner resolution. | | Required access or approval is missing | Produce a draft and evidence plan only. | | Validation or pilot behavior differs from expectation | Restore the prior state and retain the failed evidence. | | Output contains secrets or private code | Stop, quarantine the artifact, redact it, and notify the data owner. | ## Examples ### Example 1 Use two named human reviewers during a confirmed outage. ### Example 2 Stop a faulty global override and prove restored config. ## Validation - Confirm every claim against the dated sources in `references/official-docs.md`. - Verify the requested scope, owner, approval, happy path, failure path, and rollback. - Re-read the effective configuration or provider state after any approved change. - Report unsupported fields, undocumented endpoints, and unverified assumptions as failures. ## Resources - [Official documentation and contract notes](references/official-docs.md) - Re-check the dated contract before any live operation. - Treat unresolved or changed vendor behavior as a stop condition.
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace