Sentry CLI
Use this explicit skill for current Sentry command discovery and bounded
operations. Use $sentry-cli-fix-issues for an end-to-end production issue
investigation and repository fix.
Pick the right binary
| Need |
Use |
Do not substitute |
| Issues, events, traces, logs, orgs, projects, release reads, API schema |
sentry |
sentry-cli subcommand syntax |
Sourcemap inject, upload, or resolve when the installed sentry supports them |
sentry sourcemap <verb> |
sentry-cli sourcemaps plural syntax |
| Release mutations and artifact uploads |
repository wrapper or pinned sentry-cli |
ad-hoc global sentry writes |
| Legacy debug files, ProGuard, React Native artifacts |
repository wrapper or sentry-cli |
sentry subcommand syntax |
The local sentry and legacy sentry-cli executables are different CLIs.
Confirm the installed command and verb before acting:
sentry --version
sentry <noun> --help
sentry-cli --version
sentry-cli <noun> --help
Inspect first
- Check authentication without exposing credentials:
sentry auth status --json. Never use --show-token or sentry auth token.
- Confirm the target with a bounded read; specify
org/project only when
automatic detection is wrong.
- Prefer
--json, --fields, --limit, and a narrow --period; redact
customer data, headers, cookies, prompts, and payload values from reports.
Useful reads:
sentry issue list --query 'is:unresolved' --limit 20 --period 24h --json
sentry issue view ISSUE --json
sentry issue events ISSUE --limit 10 --json
sentry trace view TRACE --json
sentry log list --limit 20 --json
sentry release list --limit 20 --json
sentry project list --limit 20 --json
sentry schema issues --json
Treat sentry issue explain and sentry issue plan as advisory: verify their
claims against raw event evidence and the checked-out code.
Mutation gate
Get an explicit user decision before running commands that change remote state,
credentials, billing, or release history. Show the exact command and target
first. Use dry runs where available.
| Mutating area |
Examples |
| Issue state |
resolve, unresolve, archive, merge |
| Releases |
create, finalize, delete, archive, restore, deploy, set-commits |
| Projects, alerts, monitors |
create, delete, update, start |
| Raw API |
sentry api with non-GET method or request body |
| Artifact upload |
sentry-cli sourcemaps, debug-files, react-native, proguard |
| Local artifact rewrites |
sentry sourcemap inject / sentry-cli sourcemaps inject — dry-run first, review the diff, then apply with explicit approval |
| Authentication |
auth login, logout, refresh |
Never pass an auth token on the command line or print it. Use the CLI's normal
credential store or an approved environment variable. Confirm token scope and
org/project access before release or artifact writes.
Source-map and release evidence
Use the owning repository's package script first; it pins the right
@sentry/cli version and release/build inputs. If no wrapper exists, inspect
the exact legacy verb with sentry-cli <noun> --help before proposing a write.
Do not replace a repository's upload integration with an ad-hoc global command.
sourcemap inject rewrites local JavaScript and source-map files: run
--dry-run first, review the resulting diff, and apply only after explicit
approval. Report changed paths and diff verification in closeout, and run
git diff --check as the final whitespace validation.
Closeout
Report the binary and version used, command, read/write status, target,
bounded evidence, and verification result. Mark provider facts UNVERIFIED
until a current command or official authority proves them.
1---2name: sentry-cli3description: Sentry CLI atoms for safe issues, traces, releases, projects, sourcemaps, and deliberate mutations.4license: MIT5---67# Sentry CLI89Use this explicit skill for current Sentry command discovery and bounded10operations. Use `$sentry-cli-fix-issues` for an end-to-end production issue11investigation and repository fix.1213## Pick the right binary1415| Need | Use | Do not substitute |16| --- | --- | --- |17| Issues, events, traces, logs, orgs, projects, release reads, API schema | `sentry` | `sentry-cli` subcommand syntax |18| Sourcemap inject, upload, or resolve when the installed `sentry` supports them | `sentry sourcemap <verb>` | `sentry-cli sourcemaps` plural syntax |19| Release mutations and artifact uploads | repository wrapper or pinned `sentry-cli` | ad-hoc global `sentry` writes |20| Legacy debug files, ProGuard, React Native artifacts | repository wrapper or `sentry-cli` | `sentry` subcommand syntax |2122The local `sentry` and legacy `sentry-cli` executables are different CLIs.23Confirm the installed command and verb before acting:2425```sh26sentry --version27sentry <noun> --help28sentry-cli --version29sentry-cli <noun> --help30```3132## Inspect first33341. Check authentication without exposing credentials:35 `sentry auth status --json`. Never use `--show-token` or `sentry auth token`.362. Confirm the target with a bounded read; specify `org/project` only when37 automatic detection is wrong.383. Prefer `--json`, `--fields`, `--limit`, and a narrow `--period`; redact39 customer data, headers, cookies, prompts, and payload values from reports.4041Useful reads:4243```sh44sentry issue list --query 'is:unresolved' --limit 20 --period 24h --json45sentry issue view ISSUE --json46sentry issue events ISSUE --limit 10 --json47sentry trace view TRACE --json48sentry log list --limit 20 --json49sentry release list --limit 20 --json50sentry project list --limit 20 --json51sentry schema issues --json52```5354Treat `sentry issue explain` and `sentry issue plan` as advisory: verify their55claims against raw event evidence and the checked-out code.5657## Mutation gate5859Get an explicit user decision before running commands that change remote state,60credentials, billing, or release history. Show the exact command and target61first. Use dry runs where available.6263| Mutating area | Examples |64| --- | --- |65| Issue state | `resolve`, `unresolve`, `archive`, `merge` |66| Releases | `create`, `finalize`, `delete`, `archive`, `restore`, `deploy`, `set-commits` |67| Projects, alerts, monitors | `create`, `delete`, `update`, `start` |68| Raw API | `sentry api` with non-GET method or request body |69| Artifact upload | `sentry-cli sourcemaps`, `debug-files`, `react-native`, `proguard` |70| Local artifact rewrites | `sentry sourcemap inject` / `sentry-cli sourcemaps inject` — dry-run first, review the diff, then apply with explicit approval |71| Authentication | `auth login`, `logout`, `refresh` |7273Never pass an auth token on the command line or print it. Use the CLI's normal74credential store or an approved environment variable. Confirm token scope and75org/project access before release or artifact writes.7677## Source-map and release evidence7879Use the owning repository's package script first; it pins the right80`@sentry/cli` version and release/build inputs. If no wrapper exists, inspect81the exact legacy verb with `sentry-cli <noun> --help` before proposing a write.82Do not replace a repository's upload integration with an ad-hoc global command.8384`sourcemap inject` rewrites local JavaScript and source-map files: run85`--dry-run` first, review the resulting diff, and apply only after explicit86approval. Report changed paths and diff verification in closeout, and run87`git diff --check` as the final whitespace validation.8889## Closeout9091Report the binary and version used, command, read/write status, target,92bounded evidence, and verification result. Mark provider facts `UNVERIFIED`93until a current command or official authority proves them.
BjornMelin