Read Sentry Bug Reports
UTILITY SKILL. INVOKES: Sentry plugin or read-only Sentry API/CLI. FOR: issue lookup, event review, incident notes.
Turn Sentry data into concise incident notes. Stay read-only, redact sensitive data, and separate facts from inference. Read Sentry reporting guide for the field checklist.
USE FOR:
- Sentry issue URL, short ID, numeric issue ID, or event ID.
- Recent unresolved errors for a project, environment, or time window.
- Summaries of impact, frequency, evidence, cause, and next steps.
DO NOT USE FOR:
- Non-Sentry logs, CI failures, analytics, or general debugging without Sentry evidence.
- Code fixes, PRs, issue-status changes, or other mutations.
- Full stack-trace, payload, secret, IP, or full-email dumps.
Workflow
- Resolve the target and ambiguity.
- Confirm read-only access. Prefer the Sentry plugin; if a token is needed, ask the user to set it locally.
- Fetch only useful details: issue, recent events, and one representative event if needed.
- Report
Summary, Impact, Evidence, Likely cause, and Next steps; say if no results are found.
Troubleshooting
- Missing access: report the blocker and stop.
- Weak evidence: mark the cause uncertain.
- Multiple issues: rank by recency or volume.
Examples
Use $read-sentry-bug-reports to summarize ABC-123.Review latest unresolved production Sentry bugs in checkout.
1---2name: read-sentry-bug-reports3description: Read Sentry issue URLs, short IDs, numeric IDs, event IDs, or recent production errors. Use to summarize impact, evidence, frequency, cause, and next steps from read-only Sentry data.4---56# Read Sentry Bug Reports78**UTILITY SKILL. INVOKES:** Sentry plugin or read-only Sentry API/CLI. **FOR:** issue lookup, event review, incident notes.910Turn Sentry data into concise incident notes. Stay read-only, redact sensitive data, and separate facts from inference. Read [Sentry reporting guide](references/sentry-reporting.md) for the field checklist.1112## USE FOR:1314- Sentry issue URL, short ID, numeric issue ID, or event ID.15- Recent unresolved errors for a project, environment, or time window.16- Summaries of impact, frequency, evidence, cause, and next steps.1718## DO NOT USE FOR:1920- Non-Sentry logs, CI failures, analytics, or general debugging without Sentry evidence.21- Code fixes, PRs, issue-status changes, or other mutations.22- Full stack-trace, payload, secret, IP, or full-email dumps.2324## Workflow25261. Resolve the target and ambiguity.272. Confirm read-only access. Prefer the Sentry plugin; if a token is needed, ask the user to set it locally.283. Fetch only useful details: issue, recent events, and one representative event if needed.294. Report `Summary`, `Impact`, `Evidence`, `Likely cause`, and `Next steps`; say if no results are found.3031## Troubleshooting3233- Missing access: report the blocker and stop.34- Weak evidence: mark the cause uncertain.35- Multiple issues: rank by recency or volume.3637## Examples3839- `Use $read-sentry-bug-reports to summarize ABC-123.`40- `Review latest unresolved production Sentry bugs in checkout.`
willakins