Classify production incidents, build UTC timelines, and track action items.
npx skills add https://github.com/arbazkhan971/godmode --skill incident-arbazkhan971
Please help me install this Agent Skill. Skill: incident Source: https://github.com/arbazkhan971/godmode/tree/main/skills/incident Command: npx skills add https://github.com/arbazkhan971/godmode --skill incident-arbazkhan971
Provides a structured, repeatable process for responding to production outages and degradations, reducing time-to-detection and time-to-resolution while ensuring organizational learning through blameless post-mortems.
Invoke the incident skill by saying "/godmode:incident" and provide a concise incident summary including observed symptoms, time window, and any related deploys.
High-intent search queries and answers about installing and using this skill.
A blameless post-mortem focuses on systemic issues rather than individual mistakes. You run a guided 5-Whys root cause analysis, produce a structured template, and track actionable items with specific owners and deadlines to ensure organizational learning.
Incident severity is classified as SEV1 through SEV4. This classification establishes clear response time expectations, defines explicit escalation rules, and determines the required urgency for resolving production outages and service degradations.
The best way to build an incident timeline is using UTC-timestamped entries linked to evidence. You collect logs, deploy records, and monitoring snapshots to construct an accurate sequence of events, avoiding guesswork during root cause analysis.
MTTD and MTTR metrics are tracked by recording detection and resolution times within the UTC-timestamped incident timeline. This structured response process reduces time-to-detection and time-to-resolution for production outages.
You escalate an incident based on explicit stop and escalation rules tied to its SEV1–SEV4 classification. A guarded investigation loop tests hypotheses and keeps or discards changes based on evidence before triggering an escalation.
Root cause analysis is guided through a structured investigation loop that tests hypotheses against linked evidence. While not fully automated, this repeatable process enforces non-blaming rules and systematically identifies the source of outages.
nist0Analyze system logs to identify symptoms and design alert rules.
tranhieuttGenerate blameless postmortem documents with templates, timelines, and action items.
jnlanahanGenerate structured blameless postmortems with 5 Whys root-cause analysis.
TravisLeeeeeeTriage production alerts and coordinate structured incident response with severity classification.
