skills.rest
mattbutlerengineering
mattbutlerengineeringCOMMUNITY
Explore all skills by this author →
GitHub

sentry-triage

Convert Sentry production errors into deduplicated GitHub issues.

1|Updated Jan 24, 2026
Search Tags:#github issues#deduplication#sentry#triage#production monitoring#error filtering#ship-loop
One-click install
npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill sentry-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sentry-triage
Source: https://github.com/mattbutlerengineering/mattbutlerengineering/tree/main/.claude/skills/sentry-triage
Command: npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill sentry-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Sentry-reported production errors can pile up and remain untriaged, delaying fixes and wasting engineering time reviewing noisy or duplicate incidents.

Core Features & Use Cases

  • Queries recent production issues filtered to error/fatal events with meaningful frequency so only actionable items are considered
  • Deduplicates against existing GitHub issues using Sentry IDs and issue titles to avoid repeat tickets
  • Creates standardized ship-loop issues labeled for triage and pickup by the team
  • Use Case: After a release, automatically scan the last 14 days of Sentry errors, keep only high-signal incidents, and open at most three deduplicated GitHub issues ready for engineering follow-up.

Quick Start

Run a triage pass by setting SENTRY_ACCESS_TOKEN and executing the triage script located under the skill directory.

Frequently Asked Questions about sentry-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn Sentry production errors into GitHub issues without creating duplicates?▼

To turn Sentry errors into GitHub issues without duplicates, query Sentry for recent high-signal error events and cross-reference Sentry IDs and issue titles against existing GitHub issues before opening new labeled tickets.

What is the best way to triage Sentry errors and limit noise in production monitoring?▼

Triage Sentry errors effectively by querying a recent stats window and filtering for error or fatal events with meaningful frequency, ensuring only actionable, high-signal incidents are considered for ticket creation.

Do I need a Sentry access token to automate GitHub issue creation from production errors?▼

Yes, you need a configured Sentry access token to query production error events, alongside GitHub API authorization to search existing issues and create standardized, deduplicated triage tickets.

Can I limit the number of GitHub issues created per Sentry triage run?▼

Yes, the Sentry triage process limits ticket volume per run by filtering for high-signal incidents and opening at most three deduplicated GitHub issues ready for engineering follow-up.

How does Sentry error deduplication work when creating GitHub tickets?▼

Sentry error deduplication works by matching Sentry IDs and issue titles against existing GitHub issues, preventing repeat tickets for the same production incident during a triage pass.

What are the limitations of automated Sentry error triage for GitHub issue tracking?▼

Automated Sentry error triage is limited to a configured recent stats window and only processes error or fatal events with meaningful frequency, excluding lower-signal incidents from GitHub issue creation.

Related Skills

Explore More Software Engineering Skills→
cpfcoachingcpfcoaching

openai-sentry

Query the Sentry API for issues and events using read-only Python requests.

Community
Advanced
ConductionNLConductionNL

team-sm

Track sprint progress and blockers across OpenSpec changes and GitHub issues.

Official
Intermediate
vertivolatamvertivolatam
1

Error Tracking & Crash Reporting

Track Flutter crashes with Sentry and Firebase Crashlytics.

Official
Advanced
GainInsightDevGainInsightDev

af-integrate-sentry

Integrate Sentry error tracking into Next.js, Node, React, and Python projects.

Official
Advanced