skills.rest
fabioc-aloha
fabioc-alohaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

incident-response

Guides systematic incident triage, resolution, and post-mortem documentation for production outages.

1|Updated Mar 5, 2026
Search Tags:#rollback#post-mortem#incident response#on-call#escalation#outage#severity triage
One-click install
npx skills add https://github.com/fabioc-aloha/AlexAgent --skill incident-response-fabioc-aloha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/fabioc-aloha/AlexAgent/tree/main/plugin/skills/incident-response
Command: npx skills add https://github.com/fabioc-aloha/AlexAgent --skill incident-response-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production incidents create chaos: unclear severity, ad-hoc fixes, and forgotten lessons. This Skill provides a structured crisis-handling process so teams respond calmly, restore service quickly, and capture learnings through post-mortems. ## Core Features & Use Cases - Severity Triage: Classify incidents as P1-P4 with defined response times and escalation paths, triaging up when unsure. - Four-Phase Response: Follow Detect, Triage, Resolve, and Review phases with decision tables for rollback, hotfix, config revert, and fallback activation. - Templates & Checklists: Use the built-in post-mortem template, user/leadership communication templates, and on-call handoff checklist. - Use Case: A deploy breaks checkout for all users. Use this Skill to classify it as P1, roll back the deployment first, notify leadership within 15 minutes, and complete a post-mortem with action items within 48 hours. ## Quick Start Use the incident-response skill to triage this production outage and draft a post-mortem with timeline and action items.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I respond to a production incident step by step?▼

Follow four phases: Detect the issue via monitoring or user reports, Triage by assessing who is affected and assigning a P1-P4 severity, Resolve by rolling back or hotfixing to restore service first, then Review with a post-mortem within 48 hours.

How do I classify incident severity levels P1 through P4?▼

P1 means service down for all users requiring immediate response, P2 is a major broken feature without workaround, P3 is degraded with a workaround, and P4 is minor or cosmetic. When unsure, triage up and downgrade after investigation.

Should I rollback or hotfix during an outage?▼

Rollback first when a recent deploy caused the incident, since it is the fastest path to recovery. Revert config for config-caused issues, hotfix only when rollback is impossible, and activate fallbacks for third-party dependency failures.

What should a post-mortem template include?▼

A post-mortem includes date, severity, duration, impact summary, a UTC timeline of events, root cause via 5 Whys analysis, what went well and wrong, and an action items table with owners and due dates.

When should I not debug in production during an incident?▼

Never debug in production while users wait. The golden rule is restore service first through rollback or fallback, then investigate root cause afterward with debug logging and recent-change review.

Related Skills

Explore More Software Engineering Skills→
PostHogPostHog
713

signals-scout-insight-alerts

Triages PostHog insight alert firing history to surface missed, material firings as inbox reports.

Official
Advanced
vertivolatamvertivolatam
1

Post-Mortem Process

Guide blameless post-mortems with timeline reconstruction and 5 Whys analysis.

Official
Advanced
tyhuffman7tyhuffman7
1

investigate

Guide structured four-phase bug investigations to diagnose root causes.

Community
Advanced
haJ1thaJ1t

chaos-engineer

Executes chaos engineering experiments to inject controlled failures and test system resilience.

Community
Advanced