devops_incident_responder — Claude Code subagent for incidents
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.
no license ★ 776 updated 2026-11-12
.claude/agents/devops_incident_responder.mdWhat devops_incident_responder does
The subagent produces a Markdown incident report with severity, impact, a timeline, established facts, and evidence still needed. It ranks possible causes and suggests checks that can separate one explanation from another.
The report lays out containment, service recovery, verification, escalation, and rollback steps. It describes a likely root cause and preventive actions only when the evidence supports them. A cause remains unconfirmed if the available facts do not distinguish it from other explanations.
Inputs can include symptoms, affected services, response status, logs, metrics, health checks, deployment differences, service topology, and operator notes. The agent does not fabricate telemetry or claim access to production. For Claude Code, place the agent file at .claude/agents/devops_incident_responder.md.
What it helps with
- build an incident timeline and assess impact
- compare possible causes using discriminating checks
- plan containment and service recovery
- write verification and rollback steps
Example prompts for the agent
- Analyze this outage: the API started returning errors after the latest deployment.
- Turn these logs and metrics into an incident report.
- Compare the likely causes and outline a safe recovery plan.
How to install devops_incident_responder
Manually: put the files in place
.claude/agents/devops_incident_responder.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/devops_incident_responder.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/devops_incident_responder.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about devops_incident_responder
How do I install devops_incident_responder in Claude Code?
Add the agent file at .claude/agents/devops_incident_responder.md.
What does devops_incident_responder do?
It turns incident details and available evidence into a Markdown report with ranked hypotheses, checks, and recovery steps.
When does the subagent identify a root cause?
It names a probable cause only when evidence separates it from alternatives. Otherwise, it reports hypotheses and checks.