# devops_incident_responder

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.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/devops_incident_responder.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-devops-incident-responder

## What it 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`.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/devops_incident_responder.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/devops_incident_responder.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/devops_incident_responder.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/devops_incident_responder.md

## When to use it
- 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
- 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.

## Similar
- [devops-incident-responder](https://affpapa.org/en/nevibecode/agents/devops-incident-responder.md) — subagent · 206 installs
- [incident-responder](https://affpapa.org/en/nevibecode/agents/voltagent-community-incident-responder.md) — subagent · 265 installs
- [rootly-incident-responder](https://affpapa.org/en/nevibecode/agents/rootly-incident-responder.md) — subagent · 167 installs
- [PagerDuty Incident Responder](https://affpapa.org/en/nevibecode/agents/pagerduty-incident-responder.md) — subagent · ★ 41430 repo stars
- [agency-incident-responder](https://affpapa.org/en/nevibecode/skills/agency-incident-responder.md) — skill · ★ 85 repo stars
- [incident-runbook-templates](https://affpapa.org/en/nevibecode/skills/incident-runbook-templates.md) — skill · 10900 installs

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
