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
npx skills add OneWave-AI/claude-skills --skill incident-responder -a claude-codeWhat 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.mdwith 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.mdand 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-code2Manually: put the files in place
~/.claude/skills/incident-responder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/incident-responder/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill incident-responder -a codex2Manually: put the files in place
.agents/skills/incident-responder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill incident-responder -a cursor2Manually: put the files in place
.cursor/skills/incident-responder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills incident-responder2Manually: put the files in place
.github/skills/incident-responder/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill incident-responder -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path incident-responderManually: put the files in place
.devin/skills/incident-responder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill incident-responder -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 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.