incident-response

Orchestrate incident response workflows with classification, diagnosis, auto-fix, notification, and verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nixopus/agent --skill incident-response-nixopus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/nixopus/agent/tree/main/skills/incident-response
Command: npx skills add https://github.com/nixopus/agent --skill incident-response-nixopus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident response workflows require timely classification, diagnosis delegation, and coordinated remediation with auditable verification. This skill orchestrates severity assessment, diagnostic handoff, auto-fix decisions, stakeholder notification, and post-incident review to reduce MTTR and risk exposure.

Core Features & Use Cases

  • Severity-based event classification and prioritization to determine response urgency.
  • Delegation of diagnosis to diagnostic agents with full context and evidence gathering.
  • Decision logic to auto-fix, notify, or escalate based on root-cause analysis.
  • FIX workflow via GitHub-like automation: creating fix branches, PRs, and curated reviews (without auto-merge).
  • NOTIFY across channels to keep stakeholders informed and aligned.
  • VERIFY post-deployment checks to confirm resolution and prevent regressions.

Quick Start

When a failure is detected, run this skill to automatically classify, diagnose, decide on fixes, notify stakeholders, and verify the resolution.

Frequently Asked Questions about incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate incident response for production failures?

You can automate incident response by orchestrating classification, diagnosis delegation, auto-fix decisions, and notifications to reduce MTTR across services and infrastructure. This ensures structured escalation and safe remediation with guardrails.

What is the best way to handle incident classification and severity assessment?

Incident classification uses severity-based event prioritization to determine response urgency and trigger appropriate downstream actions. This mechanism ensures that critical production failures receive immediate attention and structured escalation.

Can I automatically create fix branches and PRs for incident remediation?

Yes, the incident response workflow creates fix branches and pull requests via GitHub-like automation without auto-merging. This ensures user-reviewed fixes are applied safely after diagnostic agents identify the root cause.

How does post-incident verification prevent regressions after deployment?

Post-deployment verification performs auditable checks to confirm incident resolution and prevent regressions. This process validates that the applied fixes have successfully remediated the production failure across affected services.

What are the limitations of automated incident response and auto-fix workflows?

Automated incident response has guardrails including no automatic merges and limited auto-fix attempts. These constraints prevent unsafe remediation actions during complex production failures across services, containers, and infrastructure events.