skills.rest
jscott3201
jscott3201COMMUNITY
Explore all skills by this author →
GitHub

incident-response

Triage production incidents by gathering symptoms, correlating changes, and guiding mitigation.

2|Updated Apr 3, 2026
Search Tags:#postmortem#triage#mitigation#root-cause#incident-response#oncall#selenedb
One-click install
npx skills add https://github.com/jscott3201/ai-agent-skills --skill incident-response-jscott3201
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/incident-response
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill incident-response-jscott3201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents panic-driven debugging during production incidents by providing a structured triage workflow that gathers symptoms, correlates recent changes, assesses severity and blast radius, guides immediate mitigation, and produces a documented postmortem.

Core Features & Use Cases

  • Rapid Triage: Collects error symptoms, affected scope, onset time, and recent deploys or config changes to focus the investigation.
  • Mitigation-first Guidance: Recommends 1–3 prioritized mitigation strategies (revert, feature flag, scale, redirect) with pros, cons, and time-to-effect to stop the bleeding quickly.
  • Cross-session Memory: When SeleneDB is available, auto-recalls prior incidents, links mitigations and root causes, and persists incidents, decisions, and postmortems to the graph for future discovery.
  • Root Cause Handoff: Transitions to systematic debugging and links RootCause chains to incident nodes so teams can trace recurring systemic failures.
  • Use Case: On-call engineer detects a surge of 500 errors after a deploy, uses the Skill to triage severity, choose a mitigation (rollback or feature flag), document the timeline, and generate a postmortem.

Quick Start

Invoke the incident-response skill with a concise description like "High error rate and timeouts after deploy to production" to begin structured triage and mitigation.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I triage a production outage after a deploy?▼

Structured triage for production incidents collects error symptoms, affected scope, onset time, and recent deploys to assess severity, then guides mitigation strategies like rollback or feature flag to stop the bleeding quickly.

What is mitigation-first incident response?▼

Mitigation-first incident response prioritizes stopping the bleeding by evaluating 1–3 mitigation strategies like revert, feature flag, scale, or redirect with pros and cons before transitioning to systematic root-cause debugging.

How do I document a postmortem after resolving an outage?▼

You document a postmortem by recording the incident timeline, mitigation decisions, and root-cause chains, then persisting these as incident, decision, and postmortem nodes for future discovery and cross-session recall.

Does incident response triage work with SeleneDB for prior incident recall?▼

Yes, when SeleneDB is available, the triage workflow auto-recalls prior incidents, links past mitigations and root causes, and persists new incident, decision, and postmortem nodes to the graph database for future discovery.

What's the best way to handle on-call regressions without panic-driven debugging?▼

The best way to handle on-call regressions is applying a structured triage workflow that correlates recent config changes, assesses blast radius, and enforces mitigation-first containment before starting systematic root-cause analysis.

When should I transition from incident mitigation to root-cause analysis?▼

You should transition from incident mitigation to root-cause analysis immediately after containment stops the bleeding, linking RootCause chains to incident nodes to trace recurring systemic failures.

Related Skills

Explore More Software Engineering Skills→
decocmsdecocms
5

deco-incident-debugging

Analyze production incidents using past learnings and live data to identify root causes.

Official
Advanced
PriyanshKuniyalPriyanshKuniyal

postmortem-writing

Create structured postmortem documents with root cause analysis, timelines, and action items.

Community
Advanced
jscott3201jscott3201
2

deferred-tracking

Detect deferral language and persist DeferredItem and Gate records to SeleneDB.

Community
Advanced
hotyanovichahotyanovicha

test

Run Playwright tests with file, browser, and debug options.

Community
Basic