investigate-sentrylisted

Investigate and triage Sentry issues with structured analysis. Fetches issue data via Sentry API (1Password CLI for auth), aggregates event patterns (releases, browsers, users, environments), cross-references AWS CloudWatch Lambda metrics, and produces an assessment document with root cause hypotheses, decision matrix, and open questions. Use when: a Sentry issue needs investigation before deciding on a fix, you want to understand event distribution patterns, you need server-side AWS cross-correlation, or you want a structured assessment to share with the team. Triggers on: investigate-sentry, sentry issue, sentry triage, sentry investigation
ArieGoldkin/claude-forge · ★ 6 · DevOps & Infrastructure · score 77

Install: claude install-skill ArieGoldkin/claude-forge

# Investigate Sentry Issue Structured investigation: pull Sentry data via API, aggregate patterns, cross-reference AWS, produce an assessment doc with decision matrix. **Core principle: Investigate before fixing. Present evidence and options, not premature solutions.** ## Workflow ### 1. Parse input Extract from arguments: - **Short ID** (e.g., `APP-2Y`) or **full Sentry URL** - **Flags**: `--skip-aws` (skip CloudWatch), `--verbose` (raw API data) ### 2. Authenticate Read token via `op` CLI, fall back to `$SENTRY_AUTH_TOKEN` env var. See `${CLAUDE_SKILL_DIR}/references/sentry-api.md` for auth pattern and error handling. ### 3. Fetch Sentry data Call four API endpoints in sequence: 1. Resolve short ID to numeric issue ID (search endpoint) 2. Get issue metadata (title, status, priority, counts, first/last seen) 3. Get events with full context (up to 100) 4. Get tag distributions (release, browser, OS, environment, URL) See `${CLAUDE_SKILL_DIR}/references/sentry-api.md` for endpoints and response parsing. ### 4. Aggregate and analyze From the raw event data, build: - **Event timeline table** — one row per event with de-identified user, release prefix, browser, URL - **Distribution analysis** — releases, browsers, environments, users, routes - **Pattern detection**: - >70% events share a release → potential regression - >70% events share a browser → browser-specific - >70% events share a route → route-specific - Scattered across all dimensions → environmenta