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".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads

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.
namesentry-incident-runbook
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy 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

  1. Check Sentry dashboard for active incidents and error spikes
  2. Classify incident severity using P0-P3 framework based on error rate and user impact
  3. Complete initial triage checklist to assess scope and gather context
  4. Use Sentry API commands to retrieve issue details and recent events
  5. Identify error pattern (deployment-related, third-party failure, data corruption, resource exhaustion)
  6. Apply appropriate resolution steps based on identified pattern
  7. Communicate status using incident templates (initial alert, updates, resolution)
  8. 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.

Resources