Skip to main content
subagent CX Codex

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

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

devops-incident-responder VoltAgent Community devops-incident-responder is a Claude Code subagent that assists with active production incidents, root-cause investigations, and blameless postmortems. CX Codex 206installs devops-incident-responder VoltAgent devops-incident-responder — a subagent for rapid analysis of CI failures, deployment issues, infrastructure problems, and service outages. CX Codex ★ 6,505repo stars incident-responder VoltAgent incident-responder handles production incident triage, containment planning, and root-cause analysis. It focuses on minimal safe interventions and clear rollback paths. CX Codex ★ 6,505repo stars rootly-incident-responder davila7 rootly-incident-responder — a Claude Code subagent for Rootly incident triage, historical matches, on-call coordination, and reviewed remediation plans. CX Codex 167installs incident-commander Alireza Rezvani incident-commander — a Claude skill that runs an outage from declaration to post-mortem: severity classification, timeline reconstruction, root-cause analysis. CX Codex +1 610installs incident-response microsoft incident-response guides SRE and operations teams through Azure incident triage, diagnostic query writing, mitigation plans, and root cause documentation. CX Codex +1 ★ 1,627repo stars sre-incident-response paulip114 sre-incident-response is a Claude Code skill that structures production outage management using Google IMAG methods. Responders deploy generic mitigations first and triage systematically. CX Codex +1 ★ 67repo stars incident-runbook-templates Seth Hobson The incident-runbook-templates skill builds step-by-step incident runbooks for detection, triage, mitigation, recovery, escalation, and status updates. CX Codex +1 10,900installs

From the same set112

The whole set →
memory-compress memory-compress shrinks the semantic memory tree by merging near-identical nodes and dropping duplicates, while key checkpoints stay put. CX Codex +1 ★ 1,357repo stars memory-prune memory-prune cleans low-value, broken, and outdated nodes from your semantic memory tree. Keeps project context lean and responsive. CX Codex +1 ★ 1,357repo stars elevenlabs-transcribe elevenlabs-transcribe is a Claude Code skill that sends audio and video files to ElevenLabs Scribe v2 and returns a transcript. Set the language, output file, or speaker count. CX Codex +1 ★ 1,357repo stars bigcommerce-api Skill for BigCommerce API: REST, GraphQL Storefront, webhooks, OAuth. Guides through integrations, headless storefronts, and marketplace app development. CX Codex +1 ★ 1,357repo stars frontend-developer frontend-developer — a React-focused subagent that builds and refactors TypeScript UI with testing and accessibility in mind. Use it for new interface work or difficult frontend changes. CX Codex ★ 1,357repo stars documentation-expert documentation-expert is a Claude Code subagent for creating and maintaining software documentation. It can handle requests for API references, user guides, and documentation structure. CX Codex ★ 1,357repo stars commit Generates task-aligned Conventional Commits, tracks status transitions, and validates changed files against task scopes. CX Codex +1 ★ 1,357repo stars incident-responder incident-responder guides production incident response, from assessing impact and coordinating roles to restoring service and documenting follow-up work. CX Codex ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open