sentry-issuelisted

# Sentry Issue Investigation Pull everything needed to debug a Sentry issue, starting from just a short ID. ## Quick start ```bash ~/.claude/skills/sentry-issue/scripts/sentry-issue.sh MY-PROJECT-4X2 ``` Accepts a short ID (`PROJECT-ABC`), a numeric issue ID, or a full issue URL (`https://<org>.sentry.io/issues/123456/`). Prints a compact digest: issue summary, tags, exception chain with in-app stack frames, request info, last 10 breadcrumbs. Full JSON payloads are saved to `/tmp/sentry-issue-<id>.json` and `/tmp/sentry-event-<id>.json` for follow-up `jq` queries. ## How auth and org resolution work - **Token**: `SENTRY_AUTH_TOKEN` env -> `./.sentryclirc` -> repo-root `.sentryclirc` -> `~/.sentryclirc`. The token is never printed. - **Org**: `--org <slug>` flag -> `SENTRY_ORG` env -> `.sentryclirc` `org` key -> auto-discovery via `GET /api/0/organizations/`. With a single accessible org it is used directly; with multiple orgs, short IDs are probed against each, while numeric IDs require `--org`. - **Server**: `SENTRY_URL` env or `.sentryclirc` `url` key for self-hosted; defaults to `https://sentry.io` (which proxies org-scoped routes to the correct region, including EU orgs). Required token scopes: `org:read`, `project:read`, `event:read`. ## Investigation workflow 1. Run the script with the identifier the user gave. 2. Read the digest: in-app frames (`[app]` prefix) point at the failing code; tags like `functionName`, `transaction`, `url`, `environmen