sentry-clilisted

# Sentry CLI Skill Use the configuration and rules below when constructing all `sentry-cli`/API commands. ## Configuration Update the table below with your Sentry organization and credential file paths: | Environment | Organization | Project | Token File | |---|---|---|---| | Production | `<your-org-slug>` | `<your-prod-project-slug>` | `~/.sentry/prod.token` | | Staging | `<your-org-slug>` | `<your-staging-project-slug>` | `~/.sentry/staging.token` | If the target environment is unclear, ask the user before running any command. ### Prerequisites (one-time setup by user) Generate a Sentry auth token (**Settings → Auth Tokens**) with `project:read`/`org:read` scope for each environment and save it to the corresponding token file. Never print or display token values. Do not perform these steps yourself. ```bash brew install getsentry/tools/sentry-cli mkdir -p ~/.sentry && echo "<your-auth-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE> ``` ## Command Format Via `sentry-cli`: ```bash SENTRY_AUTH_TOKEN="$(cat <TOKEN_FILE>)" sentry-cli --org <org-slug> <command> ``` Via API (`curl`), for operations `sentry-cli` doesn't cover: ```bash curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \ "https://sentry.io/api/0/<endpoint>" | jq . ``` ## Available Commands / Endpoints ### Read-only (safe, no confirmation needed) | Command / Endpoint | Description | |---|---| | `sentry-cli releases list --org <org> -p <project>` | List releases | | `sentry-cli releases info <vers