home / skills / jeremylongshore / claude-code-plugins-plus-skills / sentry-incident-runbook

This skill helps you manage incident response with Sentry by triaging, classifying, and documenting runbooks for faster resolution.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill sentry-incident-runbook

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
1.8 KB
---
name: sentry-incident-runbook
description: |
  Manage 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".
allowed-tools: Read, Write, Edit, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# 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
- [Sentry Issue Details](https://docs.sentry.io/product/issues/issue-details/)
- [Sentry Alerts](https://docs.sentry.io/product/alerts/)

Overview

This skill helps manage incident response procedures using Sentry to investigate production errors, triage issues, and run repeatable runbooks. It guides severity classification, initial triage, pattern identification, remediation steps, and documentation for post-incident reviews. Use it to streamline communication and ensure consistent, auditable incident handling.

How this skill works

The skill inspects active Sentry issues and recent events, pulling metadata via Sentry API commands to build context. It walks through a P0–P3 severity classification, runs a checklist to assess scope and user impact, identifies common error patterns, and suggests resolution steps. It produces structured outputs: severity, completed checklists, root-cause notes, a resolution timeline, and a postmortem template.

When to use it

  • A production error spike appears on the Sentry dashboard
  • You need to triage and prioritize a new or recurring issue
  • Preparing or executing an incident response workflow
  • Coordinating cross-team communication during outages
  • Documenting findings and producing a postmortem after resolution

Best practices

  • Verify alert rules and notification channels before incidents occur
  • Classify severity using impact and error rate, map to P0–P3 consistently
  • Complete the initial triage checklist immediately to collect reproducible context
  • Look for deployment timestamps and third-party errors to identify patterns quickly
  • Use templated messages for updates and resolution to keep stakeholders aligned
  • Record timestamps and decisions to make postmortems actionable

Example use cases

  • Investigate a sudden error rate increase after a deploy and determine rollback need
  • Triage recurring data-corruption exceptions and isolate the faulty subsystem
  • Coordinate PagerDuty and Slack notifications while documenting incident progress
  • Run a postmortem workflow after a P1 outage and generate a remediation plan

FAQ

What prerequisites are required?

You need Sentry access to project issues, configured alert rules, notification channels (Slack, PagerDuty), and a shared severity framework.

What outputs will I get from running the runbook?

A classified incident severity, completed triage checklist, documented root cause, a resolution timeline, and a postmortem report template.