Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
Incident severity classification, runbook templates, root cause analysis, and post-incident review
Install Incident Response Patterns
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vibeeval/vibecosystem incident-response-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/incident-response-patterns .claude/skills/incident-response-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .claude/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vibeeval/vibecosystem incident-response-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/incident-response-patterns .agents/skills/incident-response-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .agents/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vibeeval/vibecosystem incident-response-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/incident-response-patterns .cursor/skills/incident-response-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .cursor/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vibeeval/vibecosystem.git --path skills/incident-response-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vibeeval/vibecosystem incident-response-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/incident-response-patterns .gemini/skills/incident-response-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .gemini/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vibeeval/vibecosystem incident-response-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/incident-response-patterns .github/skills/incident-response-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .github/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vibeeval/vibecosystem incident-response-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/incident-response-patterns .opencode/skills/incident-response-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "incident-response-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/incident-response-patterns into .opencode/skills/incident-response-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-response-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
incident-response-patterns- GitHub stars
- 531
- Token cost
- ~709 tokens
- SKILL.md length
- 105 words
- Files
- 1
- Skills in repo
- 144
- Repo updated
- First seen
- Licence
- MIT
At a glance
Incident severity classification, runbook templates, root cause analysis, and post-incident review
- Tasks that involve Incident response
- SKILL.md covers Severity Classification, Incident Response Protocol, Runbook Template and Root Cause Analysis, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Runbooks and postmortems
What it does
Incident Response Patterns is an agent skill from vibeeval/vibecosystem. Incident severity classification, runbook templates, root cause analysis, and post-incident review
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Incident response, Runbooks and postmortems and Root cause analysis. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.
When your agent uses it
- Tasks that involve Incident response
- Tasks that involve Runbooks and postmortems
- Tasks that involve Root cause analysis
Example prompts
- “/incident-response-patterns”
What it can do on your machine
Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Incident Response Patterns loads about 709 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 105 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 105 words, ~709 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-response-patterns/SKILL.md (or your agent's skills folder).- name
- incident-response-patterns
- description
- Incident severity classification, runbook templates, root cause analysis, and post-incident review
Incident Response Patterns
Severity Classification
| Level | Tanım | Response Time | Escalation |
|---|---|---|---|
| SEV-1 | Tam kesinti, data loss | 5 dk | Tüm ekip |
| SEV-2 | Major feature bozuk | 30 dk | On-call + lead |
| SEV-3 | Minor feature bozuk | 4 saat | On-call |
| SEV-4 | Kozmetik, low impact | Sonraki iş günü | Ticket |
Incident Response Protocol
1. DETECT → Alert tetiklendi / kullanıcı bildirdi
2. TRIAGE → Severity belirle, incident channel aç
3. ASSIGN → Incident Commander + Responder ata
4. CONTAIN → Bleeding'i durdur (rollback, feature flag off)
5. FIX → Root cause'u düzelt
6. VERIFY → Fix'i doğrula (monitoring, smoke test)
7. RESOLVE → Incident kapat, stakeholder bilgilendir
8. REVIEW → Post-incident review (48 saat içinde)Runbook Template
# Runbook: [Service Name] - [Issue Type]
## Symptoms
- Alert: [alert name]
- Dashboard: [link]
- Expected: [normal behavior]
- Actual: [observed behavior]
## Diagnosis Steps
1. Check [metric/log/dashboard]
2. Run: `kubectl get pods -n production`
3. Check: `SELECT count(*) FROM errors WHERE ...`
## Mitigation
1. Quick fix: [rollback/restart/scale]
2. Feature flag: [disable feature X]
3. Redirect: [failover to backup]
## Escalation
- L1: [on-call engineer]
- L2: [team lead]
- L3: [CTO/VP Eng]Root Cause Analysis
5 Whys
Problem: API 500 hatası
Why 1: Database connection timeout
Why 2: Connection pool tükendi
Why 3: Slow query connection'ları tutuyor
Why 4: Missing index on frequently queried column
Why 5: Schema change review process eksik
→ Action: Schema change PR'da EXPLAIN ANALYZE zorunluPost-Incident Review Template
## Incident Summary
- Duration: [start - end]
- Impact: [affected users/revenue]
- Severity: SEV-[X]
## Timeline
- HH:MM - Alert triggered
- HH:MM - Incident declared
- HH:MM - Root cause identified
- HH:MM - Fix deployed
- HH:MM - Incident resolved
## Root Cause
[Detailed technical explanation]
## Action Items
- [ ] [Fix] Add missing index (owner: @dev, due: date)
- [ ] [Prevent] Add schema review step (owner: @lead)
- [ ] [Detect] Add connection pool alert (owner: @sre)Checklist
- Severity matrix tanımlı
- On-call rotation aktif
- Runbook'lar güncel
- Incident channel template hazır
- Post-incident review 48 saat içinde
- Action items tracked (Jira/Linear)
- Blameless culture enforced
- Alerting threshold'lar doğru
Anti-Patterns
- Blame culture (kişi değil, sistem düzelt)
- Runbook'suz servis
- Post-incident review atlamak
- Alert fatigue (çok fazla false positive)
- Hotfix without rollback plan
© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/incident-response-patterns of vibeeval/vibecosystem.
Open the folder on GitHubat commit 3b763b1
Compare with similar skills
Incident Response Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Incident Response Patterns this skillvibeeval/vibecosystem | 531 | — | ~709 | Automated safety check: Pass | MIT | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 108 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Conducting Post Incident Lessons Learnedmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Incident Postmortemgithub/awesome-copilot | 40k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Incident Postmortemrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Debug Production IssueFerroxLabs/wayland | 608 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Conducting Post Incident Lessons Learned
mukul975/Anthropic-Cybersecurity-Skills
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
- Official
Incident Postmortem
github/awesome-copilot
A skill your agent uses when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem.
Incident Postmortem
revfactory/harness-100
A full pipeline where an agent team collaborates to generate incident postmortem reports.
Debug Production Issue
FerroxLabs/wayland
Orchestrates systematic production debugging from alert through root cause identification and resolution, chaining four engineering skills into a structured diagnostic pipeline.
Incident Response Lifecycle
LeoYeAI/openclaw-master-skills
Incident response process management following the NIST 800-61 lifecycle.
More from vibeeval/vibecosystem
All 144 skills in this repoAgent Benchmark
vibeeval/vibecosystem
Framework for measuring and tracking agent response quality over time.
Differential Review
vibeeval/vibecosystem
Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.
Factcheck Guard
vibeeval/vibecosystem
A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.
Fp Check
vibeeval/vibecosystem
Systematic false positive verification for security findings.
N8n Workflows
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
Notepad System
vibeeval/vibecosystem
A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.
Related
Categories
Questions about Incident Response Patterns
What does Incident Response Patterns do?
Incident severity classification, runbook templates, root cause analysis, and post-incident review. Incident Response Patterns is an agent skill from vibeeval/vibecosystem.
When should I use Incident Response Patterns?
Incident Response Patterns fits situations like: tasks that involve Incident response; tasks that involve Runbooks and postmortems; tasks that involve Root cause analysis.
How do I install Incident Response Patterns in Claude Code?
Run `npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a claude-code`. Or copy the skill folder (skills/incident-response-patterns in vibeeval/vibecosystem) into .claude/skills/incident-response-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Incident Response Patterns in Codex?
Run `npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a codex`. Or copy the skill folder (skills/incident-response-patterns in vibeeval/vibecosystem) into .agents/skills/incident-response-patterns in your project. Codex loads it when a task matches its description.
Can I use Incident Response Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill incident-response-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-response-patterns, .gemini/skills/incident-response-patterns, .github/skills/incident-response-patterns and .opencode/skills/incident-response-patterns in your project.
What does Incident Response Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Response Patterns is instructions for the agent only.
Does Incident Response Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Incident Response Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Incident Response Patterns use?
Incident Response Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Incident Response Patterns use?
About 709 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Incident Response Patterns?
Skills that share tags, products or a category with Incident Response Patterns: Post-Incident Debrief (VeryGoodOpenSource/vgv-wingspan, 108 stars), Conducting Post Incident Lessons Learned (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Incident Postmortem (github/awesome-copilot, 40k stars) and Incident Postmortem (revfactory/harness-100, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Response Patterns?
vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.
Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.