sentry

# Sentry Operations Use this skill for live Sentry investigation workflows in the harness. Before declaring a Sentry data surface unavailable, verify the current CLI help: - Run `sentry --help` for top-level command groups. - Run `sentry <command> --help` or `sentry help <command>` before using a command shape from memory. - If a remembered plural command fails, check for the current singular command group before blocking. Prefer canonical forms such as `sentry issue list`, `sentry org list`, `sentry log list`, and `sentry trace list`. ## Workflow 1. Confirm operation and target: - Determine operation: issue, event, log, trace, org, project, replay/deep-link, Sentry product feature usage, project/team configuration, alert/monitor creation, or API query. - Resolve org from channel config: `jr-rpc config get sentry.org` - Resolve project from channel config: `jr-rpc config get sentry.project` (optional — many queries span multiple projects). - If org is missing and needed, ask the user. - If an active repository context exists (cloned repo or configured `github.repo`), check the repo root for `TELEMETRY.md` before forming queries. When present, use its query recipes, org/project mappings, and investigation pivots as repo-specific guidance. Explicit user targets, IDs, URLs, and conversation config still win. If absent, continue normally. 2. Execute via CLI: - Use `sentry <command>` for structured queries. - The runtime authenticates Sentry HTTP traffic for this skill. Do not set or print token env vars. - Read [references/cli-commands.md](references/cli-commands.md) when choosing command shapes, target formats, flags, API fallback, or troubleshooting behavior. - Read [references/sandbox-runtime.md](references/sandbox-runtime.md) before relying on sandbox credentials. - Prefer `--json` when parsing or summarizing results. - If no high-level CLI command covers the request, use `sentry api <endpoint>` before claiming the workflow is blocked. - For an explicitly requested write, follow the write workflow below. - Prefer `sentry alert metrics` for metric alerts. Use `sentry api` only when live CLI help confirms the first-class command cannot express the requested alert behavior, such as dynamic anomaly detection. - If a Sentry API call returns `401`, or clearly says the token is invalid, expired, revoked, or unauthorized, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed. - If a Sentry API call explicitly says `missing scope`, `missing scopes`, or `insufficient scope`, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed. - If a Sentry API call returns a generic `403`, `permission denied`, or otherwise indicates missing org/project access without naming missing scopes, stop and tell the user the current Sentry connection could not access the requested Sentry data. - Only mention a specific missing scope when the CLI or API error explicitly names that scope. Do not guess scope names from a generic `403`. 3. Make requested writes: - Read [references/cli-commands.md](references/cli-commands.md) for the write command shapes. Use `sentry schema <resource>` to confirm the current endpoint and fields before an API write. - Resolve the exact org, project, team, and member slugs or IDs. Ask when the target is ambiguous; do not guess. - Read the current state first. Stop on a likely duplicate (for example, a project or team with the same slug) and report it. - Change only the fields the user asked for. Do not reset or rewrite other settings. - Run the complete command with `--dry-run` first, then run it once without `--dry-run`. - Read the resource again and report what changed (before → after) with the Sentry URL. - For a destructive or irreversible change (a delete, removing a team from a project, a slug rename, or a transfer), make sure the user named that exact action in the current request. 4. Generate deep links: - For user-scoped or entity-specific views, generate URLs instead of CLI calls. - Read [references/deep-link-patterns.md](references/deep-link-patterns.md) for URL templates. 5. Report result: - Return issue details, replay links, deep links, or CLI output inline. - Include Sentry web URLs for easy navigation. ## Guardrails - Write only when the user asks for that change. - Avoid speculative Sentry CLI subcommands. Use bundled references plus live `sentry --help` output to verify current commands. - Do not print credential values. - If org is missing and needed, ask the user. - Prefer deep links over raw data dumps when linking to Sentry web UI. - Do not use this skill for repository/source-code/commit/branch/pull-request work, even if the user mentions a Sentry feature or product area.