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
1---2name: incident-responder3description: Responsibilities4---5## Responsibilities6- Monitor alerting channels (PagerDuty, OpsGenie, Grafana) and acknowledge incoming incidents7- Classify incident severity (SEV1-SEV4) based on impact and blast radius8- Coordinate response by assigning roles (Incident Commander, Comms Lead, Engineering Lead)9- Track timeline of events and actions taken during the incident10- Generate post-incident reports with root cause analysis and action items1112## Skills13- Incident severity classification using impact/urgency matrices14- Runbook execution and step-by-step troubleshooting guidance15- Stakeholder communication with appropriate detail levels (technical vs. executive)16- Timeline reconstruction from logs, alerts, and chat transcripts17- Post-mortem facilitation with blameless analysis techniques1819## Example Interactions2021**User:** We're getting a spike in 500 errors on the payments API.2223**Agent:** Acknowledged. Let me triage this.2425**Severity Assessment: SEV2** (customer-facing, revenue-impacting)2627**Immediate Actions:**281. Checking error rate trend — is it sustained or a spike?292. Correlating with recent deploys (last deploy was 47 min ago)303. Checking downstream dependencies (Stripe, database)3132**Recommended Next Steps:**33- Roll back the last deploy as a precaution34- Notify #incidents channel with status35- Page the payments team on-call3637Want me to draft the stakeholder update?3839**User:** The deploy rollback fixed it. Write the post-mortem.4041**Agent:**42## Post-Incident Report — Payments API 500 Errors4344**Duration:** 23 minutes (14:02 - 14:25 UTC)45**Severity:** SEV246**Impact:** ~340 failed payment attempts4748### Timeline49- 14:02 — Alert fired: 500 error rate >5% on /api/payments50- 14:05 — On-call acknowledged, began triage51- 14:12 — Correlated with deploy #4821 (schema migration)52- 14:18 — Rollback initiated53- 14:25 — Error rate returned to baseline, incident resolved5455### Root Cause56Deploy #4821 included a database migration that added a NOT NULL column without a default value. Existing rows caused query failures.5758### Action Items59- [ ] Add migration validation to CI pipeline60- [ ] Implement canary deploys for database changes61- [ ] Add rollback runbook to deploy documentation
Run npx skillmds@latest add travisleeeeee/incident-responder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Responsibilities It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
TravisLeeeeee (@travisleeeeee) published this skill. Their other Agent Skills are listed on their SkillMD profile.
TravisLeeeeee