Skip to main content
skill CX Codex

incident-responder · onewave-ai — Claude Code skill for incident response

The incident-responder skill investigates production incidents by checking logs and recent changes, classifying severity, and preparing recovery guidance and a report. Use it during an outage and for follow-up.

MIT 253 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill incident-responder -a claude-code
Open on GitHub

What incident-responder does

The skill gathers incident context, searches the codebase for the affected service, and checks recent Git history and relevant logs. It assigns a SEV1–4 level, traces the failure using evidence, then lays out recovery options with commands or code changes, risks, and verification steps.

Its included materials cover severity criteria, investigation procedures, diagnostic shell commands, communication templates, and checklists. After recovery, it writes incident-report.md with an event timeline, the cause chain, and prevention tasks. It must not present an unverified explanation as fact; gaps in the evidence call for more data.

The skill can draft status-page updates and messages for different audiences. For SEV1/SEV2, it also prepares an executive summary and a customer email. Prevention items in the report are assigned to owners.

What it helps with

  • trace an outage through logs and recent changes
  • classify an incident against SEV1–4 criteria
  • plan recovery steps with risks and verification
  • draft a status-page update
  • write incident-report.md with a timeline and prevention tasks

Example prompts for the agent

  • Investigate the authentication service outage: find relevant logs and recent changes, then classify its severity.
  • Suggest a recovery plan for this incident, including risks and verification steps for each option.
  • After recovery, create incident-report.md and draft a status-page update.

How to install incident-responder

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill incident-responder -a claude-code

2Manually: put the files in place

~/.claude/skills/incident-responder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/incident-responder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about incident-responder

How do I install incident-responder in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill incident-responder -a claude-code. The skill file is at ~/.claude/skills/incident-responder/SKILL.md.

What does incident-responder do?

It helps classify and investigate incidents, plan recovery, draft communications, and produce a post-incident report with prevention tasks.

What goes into the report after an incident is resolved?

incident-report.md includes an event timeline, an evidence-backed cause chain, and prioritized prevention actions with owners.

Source text

SKILL.md · MIT
---
name: incident-responder
description: Production incident response automation. Reads logs, checks recent deploys, identifies root cause, suggests fixes, drafts incident comms, creates post-mortem templates. Severity classification (SEV1-4), escalation paths, status page updates. Generates incident-report.md with timeline, root cause, impact assessment, remediation steps, and prevention measures.
tools: Read, Glob, Grep, Bash, Write, Edit, WebFetch, WebSearch
model: inherit
---

# Incident Responder

Act as an expert SRE and production incident responder. Systematically investigate, diagnose, classify, and guide an incident through resolution, then produce actionable reports, audience-specific communications, and a prevention-focused post-mortem.

## Core Principles

1. Speed over perfection: during an active incident, fast triage beats thorough analysis.
2. Evidence-based diagnosis: back every conclusion with log entries, metrics, deploy diffs, or config changes. Never guess.
3. Clear communication: write each output for its audience. Engineers get technical detail, executives get business impact, customers get reassurance and ETAs.
4. Blameless culture: focus post-mortems on systems and processes, never individuals.
5. Prevention orientation: include both immediate fixes and long-term prevention in every remediation.

## Contents

- `references/severity-matrix.md` -- SEV1-4 classification criteria, response expectations, escalation/de-escalation rules.
- `references/investigation-protocol.md` -- log sources, deploy checks, dependency and resource analysis, root cause chain, codebase patterns.
- `references/diagnostic-commands.md` -- shell commands for logs, resources, containers, databases, git history.
- `references/communication-templates.md` -- status page, internal, executive, and customer-facing templates.
- `references/incident-report-template.md` -- full `incident-report.md` structure.
- `references/escalation-and-status.md` -- escalation paths, IC responsibilities, status page cadence and rules.
- `references/checklists.md` -- declaration, verification, resolution, and post-mortem checklists.

## Workflow

1. Gather context. Ask what is broken, when it started, who is affected, what changed recently, whether a workaround exists, and whether the issue is ongoing. Search the codebase for the affected service, check git log for recent deploys, and locate relevant log files and monitoring config.

2. Classify severity. Apply the matrix in `references/severity-matrix.md`, taking the highest level matched by any criterion. State the classification, its implications, and the required response cadence.

3. Investigate. Follow `references/investigation-protocol.md`: identify log sources, check recent deployments, analyze dependencies and resources, and build an evidence-backed failure chain to a confirmed root cause. Use `references/diagnostic-commands.md` when shell access is available.

4. Recommend resolution. Prioritize the fastest safe path: rollback, then feature-flag disable, scale resources, configuration fix, dependency failover, or a targeted hotfix. For each option, give exact commands or code changes, expected time to effect, risk of the action itself, and verification steps. Confirm recovery against the verification checklist in `references/checklists.md`.

5. Draft communications. Generate the templates in `references/communication-templates.md` appropriate to the severity: status page updates for all customer-facing incidents, internal engineering updates, plus executive summary and customer email for SEV1/SEV2. Map impact to component status and follow the cadence in `references/escalation-and-status.md`.

6. Generate the incident report. After resolution, create `incident-report.md` following `references/incident-report-template.md`. Include the complete timeline with evidence, the root cause chain, and prioritized action items with owners across all prevention categories.

7. Follow up. Verify all action items are tracked, recommend the post-mortem schedule, flag any monitoring or alerting gaps, and suggest immediate hardening steps to take before the full prevention plan lands.

## Important Rules

1. Never guess at root cause. Support every conclusion with evidence. If root cause is undetermined, say so and state what additional data is needed.
2. Never assign blame to individuals. Use blameless language focused on systems, processes, and tools.
3. Never downplay impact. Communicate severe impact clearly so stakeholders can decide well.
4. Never use emojis in any output -- reports, communications, status updates, or responses.
5. Always recommend prevention. "Be more careful" is not a prevention measure; make each one specific, measurable, and assignable.
6. Always maintain the timeline. Record every significant event with a timestamp.
7. Always consider cascading effects. Investigate laterally across downstream services, not just vertically.
8. Always verify the fix through monitoring, testing, and, where possible, user confirmation.
9. Adapt to the environment. Tailor investigation and recommendations to the tools, infrastructure, and processes that actually exist.
10. Prioritize speed during active incidents and thoroughness during post-mortems.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for DevOps and infrastructure →

incident-responder by other authors comes first.

incident-responder UseAI-pro The incident-responder skill for Claude Code guides step-by-step response to OpenClaw security breaches, from containment and investigation to credential rotation and recovery. CX Codex +1 445installs devops-incident-responder VoltAgent Community devops-incident-responder is a Claude Code subagent that assists with active production incidents, root-cause investigations, and blameless postmortems. CX Codex 206installs rootly-incident-responder davila7 rootly-incident-responder — a Claude Code subagent for Rootly incident triage, historical matches, on-call coordination, and reviewed remediation plans. CX Codex 167installs agency-incident-responder huytran1120 agency-incident-responder is a Claude Code skill that leads digital forensics and security breach investigations. It guides threat containment and timeline reconstruction during cyber attacks. CX Codex +1 ★ 85repo stars PagerDuty Incident Responder official github PagerDuty Incident Responder — a GitHub Copilot subagent that works through PagerDuty incidents: reads the context, hunts for recent code changes, and proposes a fix as a pull request. CX Codex +1 ★ 41,430repo stars devops_incident_responder AgenticOrgLab The devops_incident_responder Claude Code subagent turns production incident details into a diagnosis and recovery plan. It can use logs, metrics, and deployment history when provided. CX Codex ★ 776repo stars incident-runbook-templates Seth Hobson The incident-runbook-templates skill builds step-by-step incident runbooks for detection, triage, mitigation, recovery, escalation, and status updates. CX Codex +1 10,900installs

From the same set185

The whole set →
meeting-to-tasks meeting-to-tasks parses meeting transcripts into structured action items with assignees and deadlines, catches implicit commitments, and exports tasks for issue trackers. CX Codex +1 255installs overnight-repo-auditor overnight-repo-auditor runs an autonomous overnight code audit covering security, performance, accessibility, and dependencies without prompting for confirmation. CX Codex +1 253installs cowork-deal-room The cowork-deal-room skill reviews deal-room files in five stages and produces risk findings, term comparisons, and negotiation guidance. CX Codex +1 253installs lead-scoring-model This skill analyzes your sales history and builds a lead-scoring model tied to your actual deal data. It generates documentation with scoring dimensions, thresholds, and a CRM implementation guide. CX Codex +1 253installs runbook-generator The runbook-generator skill inspects a project’s code and deployment configuration, then writes an operational runbook.md. Use it to document releases, incident response, or disaster recovery. CX Codex +1 252installs data-pipeline-builder data-pipeline-builder turns source, destination and transformation notes into a runnable ETL/ELT pipeline: Python or SQL code, an Airflow DAG, quality checks and a spec file. CX Codex +1 252installs roi-calculator roi-calculator turns your current costs, manual hours and hourly rates into a written ROI report on an AI project, with payback and sensitivity cases. CX Codex +1 252installs investor-update-writer investor-update-writer generates monthly and quarterly updates for startup investors into a structured investor-update.md file using metrics, milestones, and runway. CX Codex +1 252installs

Project sponsors

Companies that keep this analytics open