umararshad4/honey-stack / skills/incident
incident
VerifiedRespond to a production outage: assess severity, mitigate first (roll back/flip a flag/scale), investigate safely, communicate, write a blameless postmortem. Use when prod is down, degraded, or errors spike.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| agents/openai.yaml | config | 169 B |
| references/postmortem.md | markdown | 1.3 KB |
| references/runbook.md | markdown | 1.4 KB |
references/runbook.md
View on GitHub# Live investigation & roles
## Roles (separate them even solo)
- **Incident Commander** — owns the incident, decides, delegates; does not fix hands-on.
- **Comms Lead** — internal + external/status updates; shields responders from "any update?" pings.
- **Ops/SME** — investigates and executes mitigations.
- **Scribe** — timestamps every action and finding (invaluable for the postmortem).
- Solo: act as IC (decide + log) first, then ops; write the timeline as you go.
## Golden signals (Google SRE)
Latency (split success vs error latency), Traffic (demand), Errors (rate/ratio), Saturation (how full — CPU/mem/IO/queue/connections). RED = Rate/Errors/Duration for services; USE = Utilization/Saturation/Errors for resources.
## Safe on-prod investigation
Read-only: query replicas, logs, metrics, traces — not writes. Overlay the deploy timeline on error/latency dashboards. Don't restart/flush/mutate state on a hunch — you can destroy evidence or worsen the outage. Change one thing at a time and record it. No ad-hoc prod DB writes.
## Rollback vs forward-fix
Default rollback when a recent deploy correlates with onset and rollback is safe. Forward-fix only when rollback is impossible (irreversible DB migration, data already written in the new shape) or clearly riskier than a tiny known patch. A rollback across an incompatible schema migration can itself lose data — check first.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |