Skip to main content
subagent CX Codex

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

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/devops_incident_responder.md
Open on GitHub

What 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.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

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.

Similar subagents

All subagents for DevOps and infrastructure →

From the same set24

The whole set →
security_auditor security_auditor — a subagent for Claude Code runs defensive application security reviews. Inspects source code, configurations, and dependency scanner logs to report exploitable flaws. CX Codex ★ 776repo stars search_specialist The search_specialist Claude Code subagent turns an information need into focused queries and assesses retrieved sources. It returns a compact evidence set in JSON for downstream work. CX Codex ★ 776repo stars data_engineer The data_engineer Claude Code subagent designs batch and streaming data pipelines from stated requirements. It returns a Markdown specification covering data flow, quality checks, and operations. CX Codex ★ 776repo stars product_manager product_manager is a Claude Code subagent that turns a product question and available evidence into a clear decision. It helps compare options, set priorities, and define how to measure results. CX Codex ★ 776repo stars api_designer The api_designer Claude Code subagent turns product or service requirements into REST or GraphQL API contracts. It runs on API specification tasks. CX Codex ★ 776repo stars database_optimizer database_optimizer — a subagent for Claude Code, Codex, and Cursor reviews database performance evidence and proposes optimizations. It ranks bottlenecks and outlines how to measure proposed changes. CX Codex ★ 776repo stars fullstack_implementation_engineer The fullstack_implementation_engineer Claude Code subagent turns an approved feature spec into a coordinated implementation plan. It covers data, APIs, business logic, UI, migrations, and tests. CX Codex ★ 776repo stars backend_architecture_expert The backend_architecture_expert Claude Code subagent turns repository context and requirements into a backend architecture specification. It is activated for proposed changes to APIs, data, and services. CX Codex ★ 776repo stars

Project sponsors

Companies that keep this analytics open