sentrylisted
Install: claude install-skill sgtlaugh/skills
# /sentry - Sentry Issue Search
## Commands
| Input | Does | Handler |
|-------|------|---------|
| (no args) | ask what to look up | - |
| `<issue-url\|SHORT-ID\|numeric-id>` | one issue end-to-end | Issue Deep-Dive |
| `top [project] [period]` | unresolved issues by event volume | Top Issues |
| `new [period]` | issues first seen in the period | New Issues |
| `search "<text>" [period]` | issues matching a message or `error.type:<Type>` | Search |
| `fixed <issue> <release>` | did the deploy of `<release>` stop this issue? | Is It Fixed? |
Default period: `24h`. Accepted: `1h`, `6h`, `24h`, `7d`, `14d`, `30d`, `90d`. Rows: 10 by default; raise `limit` (max 100) when asked. All environments unless the user names one - then add `--data-urlencode "environment=<name>"`.
## Output contract - what the report MUST contain
For every required item: show the real artifact, OR write `Can't-determine` + the exact call that would settle it. Never fabricate a count, `file:line`, SHA, or request_id.
**Every query:**
- **Scope line** - period, projects (`all` unless filtered), environment, and the query string sent.
- **Counts labeled by window** - every number says whether it is in-period (`count`) or lifetime (`lifetime.count`). Never mix them in one column.
- **Issue identity** - `SHORT-ID` + permalink for every issue listed.
**Issue Deep-Dive also:**
- Lifetime count, users, first seen, last seen, status, handled/unhandled.
- Top exception: type, value, and the **in-app frames**