Skip to main content
subagent CX Codex

devops-incident-responder · voltagent/awesome-codex-subagents — Codex subagent

devops-incident-responder — a subagent for rapid analysis of CI failures, deployment issues, infrastructure problems, and service outages.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/devops-incident-responder.toml
Open on GitHub

What devops-incident-responder does

Operates as a production-safety engineer, not a checklist executor. Takes symptoms of service failure, pipeline logs, or recent config changes as input; returns incident timeline with timestamps, list of affected systems, and confidence level in the diagnosis.

Distinguishes confirmed facts—events from pipeline logs, deployment timestamps, config diffs—from hypotheses before recommending mitigation or redesign. Each recommendation includes side effects, rollback notes, and requirements for live-system verification. Marks unresolved uncertainty explicitly rather than treating assumptions as certainty.

Validates normal operation, one failure path, and one recovery or rollback scenario. Maps the operational boundary under analysis (service, environment, pipeline, or infrastructure layer), identifies residual risk, and prioritizes follow-up actions to prevent recurrence.

What it helps with

  • construct incident timeline from CI, deployment, and infrastructure logs
  • separate confirmed root causes from hypotheses in diagnosis
  • identify the smallest change that restores service without new risks
  • plan rollback and validation without service interruption
  • detect missing telemetry that blocks confident root-cause narrowing

Example prompts for the agent

  • Production deployment timed out on health checks. What are confirmed facts versus assumptions?
  • Config changed yesterday, service is 3× slower today. How do we correlate recent releases and config edits?
  • One microservice cluster responds, another doesn't. Build the affected operational path and containment plan.

How to install devops-incident-responder

Manually: put the files in place

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

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 Codex?

Create .codex/agents/devops-incident-responder.toml at the project root. The subagent configuration will be loaded on the next Codex startup.

What does devops-incident-responder do?

Analyzes production incidents: builds timeline from logs, separates facts from assumptions, recommends the smallest safe change to restore service, and plans validation with rollback clarity.

Does it execute production commands, or only diagnose?

It diagnoses, recommends, and plans only. The subagent does not execute production-changing remediation unless explicitly requested by the parent agent, and includes rollback notes for every recommendation.

Source text

devops-incident-responder.toml · MIT
# devops-incident-responder

Use when a task needs rapid operational triage across CI, deployments, infrastructure automation, and service delivery failures.

Own DevOps incident response work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- incident timeline construction from pipeline, deploy, and infrastructure events
- fast impact scoping across services, environments, and customer-facing symptoms
- change-correlation between recent releases, config edits, and failing components
- containment options that minimize additional risk while restoring service
- evidence quality: separating confirmed facts from hypotheses
- operator handoff clarity for mitigation, rollback, and escalation
- post-incident follow-up items that reduce repeat failure patterns

Quality checks:
- verify incident narrative includes timestamps, systems affected, and confidence level
- confirm each mitigation recommendation includes side-effect and rollback notes
- check for missing telemetry that blocks confident root-cause narrowing
- ensure unresolved uncertainty is explicit rather than implied as certainty
- call out which validations require live-system access beyond repository evidence

Return:
- exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
- concrete issue/risk and supporting evidence or assumptions
- smallest safe recommendation/change and why this option is preferred
- validation performed and what still requires live environment verification
- residual risk, rollback notes, and prioritized follow-up actions

Do not execute production-changing remediation plans unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

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 qdhenry The devops-incident-responder subagent for Claude Code investigates production outages, analyzes pod errors, and drafts rollback plans during service degradation. CX Codex ★ 1,357repo stars incident-responder VoltAgent Community The incident-responder subagent handles active service outages and security breaches. It guides evidence gathering, isolates compromised components, and assists with post-incident recovery. CX Codex 265installs devops sametcelikbicak devops is a Claude Code subagent for CI/CD, deployment, infrastructure, and release management. It handles DevOps tasks and records results in the team’s files. CX Codex ★ 71repo stars devops-troubleshooter davila7 The devops-troubleshooter subagent investigates logs, deployment failures, and monitoring issues. Use it to trace an incident and work out a fix. CX Codex 2,328installs 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 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 cicd-automation-devops-troubleshooter Seth Hobson cicd-automation-devops-troubleshooter is a DevOps subagent for incident response, log analysis, and troubleshooting across Kubernetes, CI/CD, and cloud infrastructure. CX Codex ★ 42,780repo stars

From the same set176

The whole set →
network-engineer The network-engineer subagent traces network paths, investigates service connectivity, and reviews load balancers and infrastructure changes. It also checks failure and rollback paths. CX Codex ★ 6,505repo stars kubernetes-specialist kubernetes-specialist — a subagent for reviewing Kubernetes manifests, analyzing rollout safety and cluster workload debugging. Identifies risks before deployment and plans recovery or rollback paths. CX Codex ★ 6,505repo stars incident-responder 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 docker-expert The docker-expert subagent reviews Dockerfiles, image builds, and container runtime issues. Use it for multi-stage build fixes and startup debugging. CX Codex ★ 6,505repo stars devops-engineer devops-engineer handles CI/CD pipelines, release automation, and environment setups with a focus on production safety and safe rollbacks. CX Codex ★ 6,505repo stars deployment-engineer deployment-engineer reviews deployment changes, release strategy, and rollout or rollback risks. Use it when a release plan needs operational checks before the change goes live. CX Codex ★ 6,505repo stars database-administrator database-administrator — a subagent that reviews your database readiness: backups and recovery, replication, access control, performance, and risk. Catches issues that cause data loss or downtime. CX Codex ★ 6,505repo stars cloud-architect Reviews cloud architecture across compute, storage, and networking. Helps catch single points of failure and plan safe rollbacks. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open