incident-response

Guide live production incident response with SEV classification and communication templates.

1|Updated Mar 6, 2026

Search Tags:#debugging #communication #incident response #on-call #production issues #severity classification

Ready to run

npx skills add https://github.com/chavangorakh1999/sde-skills --skill incident-response-chavangorakh1999

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured framework for responding to live production incidents, ensuring swift mitigation, clear communication, and effective root cause analysis.

Core Features & Use Cases

SEV Classification: Guides users on how to classify incidents based on impact.
Response Checklist: Offers immediate actions for SEV-1/SEV-2 incidents, including role assignment and initial fact-finding.
Investigation Guidance: Provides a checklist of common technical areas to investigate (deploys, logs, DB, infra).
Communication Templates: Includes pre-written templates for incident alerts, updates, and resolutions.
Post-Incident Actions: Outlines necessary steps after resolution, like writing postmortems.
Use Case: When a critical service goes down, this Skill helps the on-call engineer quickly assess the situation, gather the right people, investigate systematically, and communicate effectively with stakeholders.

Quick Start

Use the incident-response skill to manage a production incident with the description "API latency spikes by 500%".

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I classify the severity of a production incident?▼

To classify production incident severity, assess the blast radius and impact on users. This incident response framework provides SEV classification guidelines to determine whether a system outage or performance degradation is a critical SEV-1 or a lower severity issue.

What is the immediate action checklist for a SEV-1 production outage?▼

The immediate action checklist for a SEV-1 production outage includes assigning incident response roles, conducting initial fact-finding, and starting systematic investigation of recent deploys, logs, databases, and infrastructure to mitigate the failure.

How do I communicate with stakeholders during a live system incident?▼

To communicate during a live system incident, use pre-written communication templates for incident alerts, status updates, and resolutions. Clear communication channels ensure stakeholders receive consistent information about the production issue mitigation progress.

What steps should I take to investigate live production issues?▼

Investigating live production issues requires systematically checking recent deployments, application logs, database performance, and infrastructure health. This incident response guidance provides a structured checklist to identify the root cause of software failures.

What should I do after resolving a critical service outage?▼

After resolving a critical service outage, execute post-incident actions including writing a detailed postmortem. This documents the root cause analysis and outlines preventative measures for future production issues.

Can I use this incident response framework for performance degradation and not just full outages?▼

Yes, this incident response framework manages performance degradation alongside full system outages. It guides real-time mitigation and SEV classification for any critical software failure, including API latency spikes and partial service disruptions.