sentry-incident-runbook
Incident response procedures using Sentry.Use when investigating production issues, triaging errors,or creating incident response workflows.Trigger with phrases like "sentry incident response", "sentry triage","investigate sentry error", "sentry runbook".
When & Why to Use This Skill
This Claude skill streamlines incident response procedures by integrating with Sentry to investigate production issues and triage errors. It provides a structured framework for managing the end-to-end incident lifecycle, from initial detection and severity classification (P0-P3) to root cause analysis and postmortem documentation, ensuring faster resolution times and improved system reliability.
Use Cases
- Production Error Investigation: Rapidly identifying the root cause of application crashes or performance spikes by retrieving and analyzing Sentry issue details.
- Automated Incident Triaging: Systematically classifying errors based on user impact and frequency to prioritize engineering efforts effectively.
- Standardized Runbook Execution: Following consistent, step-by-step procedures for common failure patterns like deployment-related errors or resource exhaustion.
- Incident Communication and Reporting: Generating structured status updates and comprehensive postmortem reports to keep stakeholders informed and document lessons learned.
| name | sentry-incident-runbook |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Sentry Incident Runbook
Prerequisites
- Sentry account with access to project issues
- Alert rules configured for critical errors
- Team notification channels set up (Slack, PagerDuty)
- Understanding of error severity classification
Instructions
- Check Sentry dashboard for active incidents and error spikes
- Classify incident severity using P0-P3 framework based on error rate and user impact
- Complete initial triage checklist to assess scope and gather context
- Use Sentry API commands to retrieve issue details and recent events
- Identify error pattern (deployment-related, third-party failure, data corruption, resource exhaustion)
- Apply appropriate resolution steps based on identified pattern
- Communicate status using incident templates (initial alert, updates, resolution)
- Document findings and complete postmortem checklist after resolution
Output
- Incident severity classification
- Triage checklists completed
- Root cause documented
- Resolution timeline recorded
- Postmortem report generated
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.