incident-response-patterns
Incident severity classification, runbook templates, root cause analysis, and post-incident review
npx skills add vibeeval/vibecosystem --skill incident-response-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```markdown # 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: [di
- Severity Classification
- Incident Response Protocol
- Runbook Template
- Root Cause Analysis
- 5 Whys
- Post-Incident Review Template
- Checklist
- Anti-Patterns
What does the incident-response-patterns skill do?
Incident severity classification, runbook templates, root cause analysis, and post-incident review
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill incident-response-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.