HigorAlves/orc / codex/orc/content/skills/incident
incident
VerifiedLive incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| references/PHASE-1-INTAKE.md | markdown | 2.2 KB |
| references/PHASE-2-ASSESS.md | markdown | 2.1 KB |
| references/PHASE-3-MITIGATE.md | markdown | 2.1 KB |
| references/PHASE-4-ROOT-CAUSE.md | markdown | 1.5 KB |
| references/PHASE-5-STABILIZE.md | markdown | 1.7 KB |
references/PHASE-5-STABILIZE.md
View on GitHub<!-- orc-incident/P5 -->
_Loaded on demand (orc-phases protocol). Do not run this phase from memory — this file is the phase._
# Phase 5 — Stabilize and hand off
1. Declare stable only with the evidence listed below.
2. Append the resolution row to the timeline with the UTC timestamp.
3. Mark the session `status: completed` in `.orc/orc.json`.
4. Bump the checkpoint to phase=done with the paths to `timeline.md`, `evidence.md` and `diagnosis.md`.
5. Print the handoff callout below.
6. Ask via `the available user-question tool (or ask in chat)` with the three options below.
7. On "Run now", invoke `$orc-postmortem`; pass the severity so its Phase 2 confirms, not proposes.
8. During its Phase 4, Read the incident `timeline.md` and convert the rows (mapping below).
9. Ask the user only to fill gaps.
10. On "Skip" for SEV-1 or SEV-2, note the declined postmortem in the timeline.
Evidence for "stable": the error rate is back to baseline (`sentry issue view` shows a stale `lastSeen` or a resolvable issue, or the user confirms the dashboard), and a mitigation or fix is in place.
Handoff callout:
```markdown
> **➡️ Next**
>
> Incident stable. Run `$orc-postmortem <slug> --severity <sev-tier>` — its Phase 4 builds the timeline FIRST, and `.orc/<branch>/files/incident/timeline.md` is that timeline, already timestamped. Point it there instead of reconstructing from memory; `evidence.md` and `diagnosis.md` feed its root-cause phase.
```
`the available user-question tool (or ask in chat)` options:
- "Run $orc-postmortem now (seeded from the timeline)"
- "Later — the timeline file will be waiting"
- "Skip — no postmortem for this one"
Row mapping into the postmortem timeline table: detection → response → mitigation → resolution.
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 |