sentry-issue-investigation
Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/sentry-issue-investigation && cp -r /tmp/sentry-issue-investigation/examples/plugin-packages/sentry/skills/sentry-issue-investigation ~/.claude/skills/sentry-issue-investigationSKILL.md
# 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.
Create deterministic animation and transitions for the active iPollo Video project.
Inspect, validate, preview, and render the active iPollo Video project with its bundled HyperFrames CLI.
Apply the core composition, timing, media, and determinism contract used by iPollo Video.
Plan visual direction, typography, pacing, audio, and composition for iPollo Video projects.
Build seek-safe keyframe animation for the active iPollo Video timeline.
Reuse approved HyperFrames blocks and components inside the active iPollo Video project.
Route video creation and editing through the active iPollo Video project and its built-in HyperFrames runtime.
Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.