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.
npx skills add composio-community/awesome-codex-skills --skill sentry-triage --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```bash curl -fsSL https://composio.dev/install | bash composio login composio link sentry # auth token with event:read + project:read ``` ## Discover Tools ```bash composio search "get sentry issue" --toolkits sentry composio search "list events for issue" --toolkits sentry composio tools list sentry ``` 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): ```bash composio execute SENTRY_GET_AN_ISSUE -d '{"issue_id":"PROJ-1F4"}' ``` 2. **Grab the latest event** with full stack + breadcrumbs
- When to Use
- Prereqs
- Discover Tools
- Diagnose a Single Issue
- Triage a Batch
- Workflow File
- Route to Linear / Slack
- Troubleshooting
curl -fsSL https://composio.dev/install | bash
composio login
composio link sentry # auth token with event:read + project:read
composio search "get sentry issue" --toolkits sentry
composio search "list events for issue" --toolkits sentry
composio tools list sentry
composio execute SENTRY_GET_AN_ISSUE -d '{"issue_id":"PROJ-1F4"}'
composio execute SENTRY_LIST_AN_ISSUES_EVENTS \
composio execute SENTRY_UPDATE_AN_ISSUE \
composio execute SENTRY_LIST_A_PROJECTS_ISSUES -d '{What does the sentry-triage skill do?
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.
How do I install it?
Run `npx skills add composio-community/awesome-codex-skills --skill sentry-triage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From composio-community/awesome-codex-skills, a repository with 15,591 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.