incident-commander · borghei — Claude Code skill: install and use
incident-commander — a skill for Claude Code guides production incident response: it scores severity, rebuilds timelines, and drafts postmortems. It also runs on Codex, Cursor, and other platforms.
LicenseRef-MIT-Commons-Clause 125 installs ★ 1,183 updated 2026-11-08
npx skills add borghei/Claude-Skills --skill incident-commander -a claude-codeWhat incident-commander does
During a live incident, it helps assess impact, choose severity, assign an incident commander, prepare updates, and track mitigation steps. Diagnosis comes after mitigation, so the workflow does not start an RCA while the service is still affecting users.
For a post-incident review, it combines events from alerts, chats, and deployments into a timeline, calculates MTTD, time to mitigate, and MTTR, then drafts an RCA with action items. Each action item gets an owner, priority, and deadline. The available RCA approaches include 5 Whys, Fishbone, and Bow Tie.
The package includes Python scripts for severity scoring, incident classification, timeline reconstruction, and postmortem generation. They are run with python3 and accept the JSON shapes described by the tools. A live incident stays focused on mitigation first.
What it helps with
- classify the severity of an active incident
- reconstruct a timeline from mixed event sources
- draft internal and status-page communications
- produce a postmortem with RCA and owned action items
Example prompts for the agent
- Classify the incident in
assets/sample_incident_data.jsonand print the result as Markdown. - Rebuild the timeline from
assets/sample_timeline_events.json, detect phases, and report gaps. - Create a post-incident review from
assets/sample_incident_pir_data.jsonwith thefishboneRCA method and action items.
How to install incident-commander
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill incident-commander -a claude-code2Manually: put the files in place
~/.claude/skills/incident-commander/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/incident-commander/
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill incident-commander -a codex2Manually: put the files in place
.agents/skills/incident-commander/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill incident-commander -a cursor2Manually: put the files in place
.cursor/skills/incident-commander/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install borghei/Claude-Skills engineering/incident-commander/SKILL.md2Manually: put the files in place
.github/skills/incident-commander/SKILL.md1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill incident-commander -a gemini-cli2Platform CLI
gemini skills install https://github.com/borghei/Claude-Skills --path engineering/incident-commanderManually: put the files in place
.devin/skills/incident-commander/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill incident-commander -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about incident-commander
How do I install incident-commander in Claude Code?
Run npx skills add borghei/Claude-Skills --skill incident-commander -a claude-code. The skill file will be placed at ~/.claude/skills/incident-commander/SKILL.md.
What does incident-commander do?
It supports production response from severity assessment and coordination through mitigation, timeline reconstruction, RCA, and postmortem writing. It also drafts communications and follow-up actions.
Should RCA start while an incident is active?
No. The workflow puts mitigation first, such as rolling back a change or failing over, and moves root-cause analysis to the post-incident review.
Similar skills
All skills for DevOps and infrastructure →incident-commander by other authors comes first.