skills.rest
Devin-AXIS
Devin-AXISCOMMUNITY
Explore all skills by this author →
GitHub

sentry-issue-investigation

Investigate Sentry issues using event, stack, tag, and release evidence before proposing fixes.

5.3k|976|Updated Aug 25, 2025
Search Tags:#stack trace#Sentry#Debugging#Root Cause Analysis#error tracking#issue investigation#release monitoring
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill sentry-issue-investigation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sentry-issue-investigation
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/sentry/skills/sentry-issue-investigation
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill sentry-issue-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging production errors from a Sentry issue title or a single stack trace often leads to wrong conclusions and wasted effort. This Skill enforces an evidence-based investigation workflow that examines bounded event data before any code change is proposed.

Core Features & Use Cases

  • Scoped Evidence Gathering: Resolves the organization, project, environment, issue, and time window, then reads representative recent events instead of trusting the issue summary.
  • Comparative Analysis: Compares stack frames, exception values, tags, releases, affected users, and recurrence patterns to separate observed failure, likely trigger, and suspected code path.
  • Minimal Evidence-Backed Fixes: When implementation is requested, inspects the matching code and applies the smallest fix supported by the evidence.
  • Use Case: A Sentry alert fires for a spike in TypeErrors after a release. Use this Skill to compare events across releases and tags, identify the suspected code path, and produce a minimal fix without exposing user payload data.

Quick Start

Investigate the Sentry issue for project web-app in production from the last 24 hours and propose a minimal fix based on the event evidence.

Frequently Asked Questions about sentry-issue-investigation

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

FAQPage Schema
How do I investigate a Sentry issue before fixing the code?▼

Start by resolving the organization, project, environment, issue, and time window, then read representative recent events. Compare stack frames, exception values, tags, and releases to separate the observed failure from the suspected code path before making any change.

How to find the root cause of a Sentry error across releases?▼

Compare events across releases and environments to spot recurrence patterns and affected users. Correlate stack frames and tags with the release timeline to identify the likely trigger rather than relying on a single stack trace.

Can I determine root cause from a Sentry issue title alone?▼

No. A title or single stack trace is insufficient evidence for root cause. You must examine representative recent events, compare tags and releases, and explicitly separate observed failure, likely trigger, and remaining uncertainty.

Does Sentry issue investigation expose user data from events?▼

It should not. The investigation workflow explicitly prohibits exposing user data from event payloads, so analysis focuses on stack frames, exception values, tags, and release metadata rather than personal payload contents.

What is the smallest safe fix for a Sentry-reported bug?▼

Inspect the code matching the suspected path identified from event evidence, then make the smallest change directly supported by that evidence. Avoid speculative refactors that go beyond what the observed failure demonstrates.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

sentry-integration

Integrate Sentry error tracking and performance monitoring in React/Next.js applications.

Official
Intermediate
troykellytroykelly
10

sentry-code-review

Parse Sentry comments on GitHub Pull Requests and implement suggested fixes.

Community
Intermediate
elasticelastic
546

observability-service-health

Assess APM service health by querying Observability APIs and Elasticsearch.

Official
Advanced
reliant-labsreliant-labs
4

reproduce

Reproduce software bugs with diagnostic logging and minimal e2e triggers.

Official
Intermediate