| name | sentry-triage |
| description | Triage WorldMonitor Sentry issues — classify unresolved events as noise, already-fixed, product bugs, or needs-human; optionally ship a tested fix. Use when the user says triage Sentry, pastes a WORLDMONITOR-* ID or sentry.io URL, or asks to investigate production errors. |
Sentry triage
Convert the old Claude command .claude/commands/sentry-triage.md into a Cursor Agent Skill. Run this playbook in the current conversation. Do not invent a parallel workflow.
Invocation input
The issue or mode is whatever this skill was invoked with — a Sentry URL, a short ID like WORLDMONITOR-Y4, a description ("Failed to fetch since the deploy"), or a mode word such as active. Read that input from the current prompt or calling skill; do not look for a harness substitution token.
- Report-only (default): classify and recommend. Do not mutate Sentry, commit, push, or open a PR unless the user already asked for that.
- Active: the user said
active, "fix it", "ship a fix", or otherwise asked for code changes. Then follow the normal WorldMonitor delivery path for any product bug you take on.
If nothing was provided, triage the unresolved board. Confirm the top candidate before going deep when several issues look equally urgent.
Prerequisites
- Sentry MCP is connected. Discover org/project with
find_organizations / find_projects if needed.
- Defaults for this repo: organization
elie-habib (https://us.sentry.io), project worldmonitor. Short IDs look like WORLDMONITOR-12A.
- Direct tools:
search_issues, search_events, analyze_issue_with_seer, update_issue. Richer reads (issue details, a specific event, tag distributions, traces) go through / or .
