sentrylisted

# /sentry — error monitoring (multi-org) REST against `https://sentry.io/api/0/` (or self-hosted Sentry instance). Bearer auth with API token. Profiles isolate org/project pairs. Arguments: `$ARGUMENTS`. Profile resolution: `--profile <name>` → `SENTRY_PROFILE` → `~/.sentry/active_profile` → `[default]`. ## Overview REST against `https://sentry.io/api/0/` (or self-hosted). Bearer auth with API token. Profiles isolate org/project pairs. Default summary view (no PII) — opt-in `--full` for raw stacktraces. ## When to Use - Investigating issues during incidents (latest unresolved, last 24h) - Resolving or assigning issues to teammates - Release health (new issues per release, commit count) - Self-hosted Sentry instances (`api_url` per profile) - Triaging error spikes across multiple projects in one org ## When NOT to Use - Sending events to Sentry → use the SDK in your app, not this skill - Bulk operations on hundreds of issues → use Sentry's UI bulk actions - Sourcemap upload → use `@sentry/cli` or Webpack/Vite plugin - User management at scale → Sentry's admin UI ## Dependencies `curl`, `jq`. ## Profile config `~/.sentry/credentials` (mode 600): ```ini [default] api_url = https://sentry.io/api/0 auth_token = sntrys_xxxxxxxxxxxxxxxxxxxxxxxx org = my-org-slug project = backend [work] api_url = https://sentry.example.com/api/0 # self-hosted auth_token = sntrys_xxxxxxxxxxxxxxxxxxxxxxxx org = company-org project = api [client_a] api_url = https://sentry.io/api/0 au