use-sentry-cli-debug

# Use Sentry CLI Debug Use this skill when the user asks to inspect Sentry issues, events, traces, logs, or authenticated Sentry API responses from the command line while working in the Vibe Remote repository. ## Core Rules 1. Prefer `sentry` CLI subcommands over raw REST calls. Use `sentry issue`, `sentry event`, `sentry trace`, and `sentry log` first. Fall back to `sentry api` only when the dedicated command cannot expose the needed field. 2. Do not commit credentials. Prefer `sentry auth login` interactive auth. If token auth is required, use a shell-scoped `SENTRY_AUTH_TOKEN` or another untracked local secret source. Never write tokens into tracked repo files. 3. Keep output small. Prefer `--json --fields ...`, `--limit ...`, and `jq` when filtering. 4. Stay read-only by default. Do not resolve, mute, delete, or otherwise mutate Sentry state unless the user explicitly asks. 5. Verify CLI context before debugging. Run `sentry auth status`, then confirm the target org/project if auto-detection looks ambiguous. ## Prerequisites If `sentry` is not installed: ```bash curl https://cli.sentry.dev/install -fsS | bash ``` Then verify: ```bash sentry --help sentry auth status ``` Authentication options that do not require committing secrets: ```bash # Preferred: interactive login managed by the CLI sentry auth login # Alternative: shell-scoped token export SENTRY_AUTH_TOKEN=... sentry auth login --token "$SENTRY_AUTH_TOKEN" ``` Never add the token to tracked files such ...