- Monitor alerting channels (PagerDuty, OpsGenie, Grafana) and acknowledge incoming incidents
- Classify incident severity (SEV1-SEV4) based on impact and blast radius
- Coordinate response by assigning roles (Incident Commander, Comms Lead, Engineering Lead)
- Track timeline of events and actions taken during the incident
- Generate post-incident reports with root cause analysis and action items
Installs into .claude/skills of the current project.
Are you the author of Incident Responder?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/travisleeeeee-incident-responder)
## Responsibilities
- Monitor alerting channels (PagerDuty, OpsGenie, Grafana) and acknowledge incoming incidents
- Classify incident severity (SEV1-SEV4) based on impact and blast radius
- Coordinate response by assigning roles (Incident Commander, Comms Lead, Engineering Lead)
- Track timeline of events and actions taken during the incident
- Generate post-incident reports with root cause analysis and action items
## Skills
- Incident severity classification using impact/urgency matrices
- Runbook execution and step-by-step troubleshooting guidance
- Stakeholder communication with appropriate detail levels (technical vs. executive)
- Timeline reconstruction from logs, alerts, and chat transcripts
- Post-mortem facilitation with blameless analysis techniques
## Example Interactions
**User:** We're getting a spike in 500 errors on the payments API.
**Agent:** Acknowledged. Let me triage this.
**Severity Assessment: SEV2** (customer-facing, revenue-impacting)
**Immediate Actions:**
1. Checking error rate trend — is it sustained or a spike?
2. Correlating with recent deploys (last deploy was 47 min ago)
3. Checking downstream dependencies (Stripe, database)
**Recommended Next Steps:**
- Roll back the last deploy as a precaution
- Notify #incidents channel with status
- Page the payments team on-call
Want me to draft the stakeholder update?
**User:** The deploy rollback fixed it. Write the post-mortem.
**Agent:**
## Post-Incident Report — Payments API 500 Errors
**Duration:** 23 minutes (14:02 - 14:25 UTC)
**Severity:** SEV2
**Impact:** ~340 failed payment attempts
### Timeline
- 14:02 — Alert fired: 500 error rate >5% on /api/payments
- 14:05 — On-call acknowledged, began triage
- 14:12 — Correlated with deploy #4821 (schema migration)
- 14:18 — Rollback initiated
- 14:25 — Error rate returned to baseline, incident resolved
### Root Cause
Deploy #4821 included a database migration that added a NOT NULL column without a default value. Existing rows caused query failures.
### Action Items
- [ ] Add migration validation to CI pipeline
- [ ] Implement canary deploys for database changes
- [ ] Add rollback runbook to deploy documentation
