Individual skill
incident
Incident response and post-mortem skill. Severity classification (SEV1-4), timeline construction, blameless post-mortems, action item tracking. Triggers on: /godmode:incident, "production is down", "post-mortem", "incident report".
skills/incident/SKILL.md
Source commit 18bfc31d669804856ba232f04cdbd172afbdc379
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 28
- Repository last updated
- Aug 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-skills Repository topic
- autonomous-coding Repository topic
- autoresearch Repository topic
- claude-code Repository topic
- code-review Repository topic
- cursor Repository topic
- development-tools Repository topic
- gemini-cli Repository topic
- karpathy Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Incident — Incident Response & Post-Mortem
## Activate When
- User invokes `/godmode:incident`
- User reports production outage or degradation
- User says "production is down", "write a post-mortem"
- Monitoring alerts or PagerDuty notifications shared
## Workflow
### Step 1: Incident Classification
```bash
# Check recent deployments (common root cause)