devops-incident-responder · qdhenry — Claude Code subagent setup
The devops-incident-responder subagent for Claude Code investigates production outages, analyzes pod errors, and drafts rollback plans during service degradation.
no license ★ 1,357 updated 2026-03-01
.claude/agents/devops-incident-responder.mdWhat devops-incident-responder does
The subagent operates as an on-call engineer handling production breakdowns. It correlates log streams, checks network latency, evaluates Kubernetes pods via kubectl, and prepares targeted fixes or deployment rollbacks.
Under the hood, the agent runs on the sonnet model. It relies on utilities like Bash, Grep, and Task, alongside external MCP integrations sequential-thinking and context7. The workflow stresses low-impact diagnostics during triage.
Without sequential-thinking and context7 configured in your environment, the agent cannot run its structured reasoning and doc lookup routines. Output includes a root cause report, remediation commands, and post-mortem notes.
What it helps with
- isolate root causes from production log streams
- diagnose failing pods inside Kubernetes clusters
- plan deployment rollbacks during service degradation
- generate blameless post-mortem reports with follow-up tasks
Example prompts for the agent
- Help me diagnose why this Kubernetes pod is crashing and propose a rollback plan.
- Analyze these API timeout logs to isolate where failures started.
- Draft a blameless post-mortem report and suggest Prometheus alert queries.
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 to install devops-incident-responder in Claude Code?
Place the subagent definition file at .claude/agents/devops-incident-responder.md inside your repository.
What does devops-incident-responder do?
It triages live system failures, inspects container logs, identifies bottlenecks, and provides concrete recovery commands.
Which MCP servers does this subagent require?
It depends on sequential-thinking for step-by-step incident reasoning and context7 for fetching library documentation.
Similar subagents
All subagents for DevOps and infrastructure →devops-incident-responder by other authors comes first.