incident-response

Guide production incident response through diagnosis, mitigation, and post-incident review.

1|Updated Mar 5, 2026

Search Tags:#troubleshooting #DevOps #incident response #SRE #production support #outage management

Ready to run

npx skills add https://github.com/baphled/dotopencode --skill incident-response-baphled

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/baphled/dotopencode/tree/main/skills/incident-response
Command: npx skills add https://github.com/baphled/dotopencode --skill incident-response-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to quickly diagnose, mitigate, and resolve production incidents, minimizing downtime and learning from failures.

Core Features & Use Cases

Rapid Diagnosis & Mitigation: Quickly identify the cause of an incident and apply immediate fixes to restore service.
Systematic Resolution: Address the root cause of the issue to prevent recurrence.
Learning & Improvement: Ensure that lessons learned from incidents are captured and applied.
Use Case: When a critical service alert fires, this Skill guides the team through the necessary steps to bring the service back online and then fix the underlying problem.

Quick Start

Use the incident-response skill to handle the P1 alert regarding the checkout service.

Frequently Asked Questions about incident-response

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

FAQPage Schema

What is the best way to manage production incidents and minimize downtime?▼

Incident response uses OODA loops and severity classification to guide teams through diagnosis, mitigation, and resolution. This structured approach systematically addresses critical service alerts and outages.

How do I resolve a critical service outage without skipping post-incident learning?▼

Resolve outages by applying immediate fixes to restore service, then addressing the root cause to prevent recurrence. Post-incident reviews capture lessons learned to improve future production support.

Can I use this framework for SRE incident severity classification and OODA loop responses?▼

Yes, this framework supports SRE incident severity classification and guides response sequences using OODA loops. It structures mitigation and resolution steps while highlighting anti-patterns to avoid during critical events.

What anti-patterns should I avoid during DevOps incident response?▼

Common anti-patterns during incident response include attempting to root-cause before mitigating the active outage. The framework emphasizes restoring service first, then systematically diagnosing and resolving the underlying issue.

How do I troubleshoot a P1 alert for a critical production service?▼

Troubleshoot a P1 alert by classifying the incident severity and following a structured response sequence. Apply immediate mitigation to bring the service online, then execute systematic resolution for the root cause.