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

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.