sentry-triage

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

By composio-community · 426 installs

npx skills add composio-community/awesome-codex-skills --skill sentry-triage

Source repository · Upstream listing

Sentry Triage Pull Sentry issues, events, and suspect commits straight into the agent via the [Composio CLI](https://docs.composio.dev/docs/cli). Skip the copy paste stack trace dance. When to Use New Sentry alert and you want the agent to investigate, not just quote the subject line. Diagnosing a regression: find the releases, suspect commit, and affected files. Building a "top 10 unresolved issues" digest with reproduction hints. Prereqs Discover Tools Common slugs (verify with get schema ): SENTRY GET AN ISSUE SENTRY LIST AN ISSUES EVENTS SENTRY RETRIEVE AN EVENT FOR A PROJECT SENTRY LIST A PROJECTS ISSUES SENTRY UPDATE AN ISSUE Diagnose a Single Issue 1. Fetch the issue (by short ID like PROJ 1F4 or numeric ID): 2. Grab the latest event with full stack + breadcrumbs: 3. Map each frame to local source. For each filename + lineno in the stack, the agent opens the file and reads ±20 lines. No manual copy paste. 4. Check suspect commits (Sentry attaches these when release tracking is set up) — open them with git show <sha locally. 5. Propose a fix with a diff, run tests, and — once green — mark the issue resolved: Triage a Batch Pipe into jq for a ranked summary: Workflow File scripts/sentry diag.ts , run with composio run file scripts/sentry diag.ts id PROJ 1F4 : The agent then reads each file at line ± 20 and drafts a patch. Route to Linear / Slack Chain tools to open a ticket for the top unresolved issue: Troubleshooting 404 on issue id → use the short ID ( PROJ 1F4 ), not the URL slug. Empty events → the issue was resolved/archived; query with query:"is:resolved" or bump limit . Missing suspect commit → release tracking isn't configured in Sentry; set up sentry cli releases in CI. No inApp frames → source maps not uploaded; stack will only show vendor code. Full CLI reference: [docs.composio.dev/docs/cli](https://docs.composio.dev/docs/cli)