Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /orc:incident
Run an incident while it happens: triage the evidence, size the blast radius, choose mitigate-first or root-cause-first, and keep a UTC timeline that becomes the postmortem's spine. Stop the bleeding before you study the wound; `/orc:postmortem` learns from the incident afterwards.
## Arguments
- First argument (free-form) — a Sentry issue short ID or URL, a pasted stack trace, or a described symptom.
- `--severity sev-1|sev-2|sev-3` — optional. Skips the severity proposal in P2; P2 still assesses the blast radius.
NOTE: a Sentry short ID looks like `PROJ-123`; `orc:sentry-cli` pulls it live. A symptom reads like "checkout is 500ing since the 14:00 deploy".
## Preconditions
> **🛑 No production mutations**
>
> P3 previews rollbacks, flag flips and scaling calls; the user executes them. orc records; the human acts.
- A `loose` context stops the run in Phase 0: there is no state dir to write.
- Every action or finding in any phase appends a UTC row to `timeline.md` in the same turn.
- Timestamps come from `date -u +%Y-%m-%dT%H:%M:%SZ`.
## Phases
…
The line at the top of this page pins the label git:20261020.7a1f356, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4011 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
higoralves/orc · 7 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lbvlyjehkp3c6h3p
GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/incident
GET https://markdownregistry.com/api/v1/blob/13618553f1e0b191d29822008954fd51f396f9c488a6d394ac19858271eb3558
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
higoralves/orc · orc/skills/adr-writing/SKILL.md · Author and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in…
higoralves/orc · orc/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test…
higoralves/orc · orc/skills/callouts/SKILL.md · The orc callout palette — emoji-header blockquotes in conversation, GitHub-flavored [!TYPE] form for GitHub-bound output
higoralves/orc · orc/skills/ci-routing/SKILL.md · The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the…
higoralves/orc · orc/skills/code-discovery/SKILL.md · Use when discovering or navigating a codebase before planning, implementing, debugging, or refactoring — prefer a…
jikig-ai/soleur · plugins/soleur/skills/incident/SKILL.md · This skill should be used when scaffolding a redaction-gated post-incident report (PIR) after a production incident.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/incident/SKILL.md · WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.opencode/skills/incident/SKILL.md · WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;
lamngockhuong/aiteamkit · plugins/atk/skills/incident/SKILL.md · Run a production incident and close it properly: a timeline built from evidence, impact and severity, the proven root…
greglas75/zuvo · skills/incident/SKILL.md · Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill…
umararshad4/honey-stack · skills/incident/SKILL.md · Respond to a production outage: assess severity, mitigate first (roll back/flip a flag/scale), investigate safely…