Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Devin-AXIS/iPolloWork --skill sentry-issue-investigation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sentry Issue Investigation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/devin-axis-sentry-issue-investigation)More formats (shields.io, HTML) on the badges page.
---
name: sentry-issue-investigation
description: Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
disable-model-invocation: false
---
# Sentry Issue Investigation
1. Resolve the organization, project, environment, issue, and time window.
2. Read representative recent events rather than assuming the issue summary is complete.
3. Compare stack frames, exception values, tags, releases, affected users, and recurrence patterns.
4. Separate the observed failure, likely trigger, suspected code path, and remaining uncertainty.
5. When implementation is requested, inspect the matching code and make the smallest evidence-backed fix.
Do not expose user data from event payloads. Do not claim root cause from a title or one stack trace alone.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...