RevampKeyRevampKey home
Download

Triage Sentry issues with AI

Ranks your unresolved Sentry issues by users affected, groups duplicates, separates real bugs from noise, and proposes assign, resolve or ignore for each one, with changes applied only after you approve.

Asks before writingUses 6 Sentry toolsWorks in RevampKey, Claude Code, Codex and Cursor

Use in RevampKey

Get RevampKey to connect Sentry

RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Sentry is one click away with its skills already attached.

Download RevampKey

Not now? Use the skills in your current tool

curl -fsSL --create-dirs -o .claude/skills/sentry-issue-triage/SKILL.md https://revampkey.com/marketplace/sentry/skills/issue-triage/SKILL.md
Other agents
Other agents

When to use it

  • The Sentry inbox is out of control
  • Weekly error-budget review
  • Before an on-call handover

What it looks like

You

Help me clean up unresolved issues in api-prod.

find_projectsfind_issuesget_issue_detailsfind_teams+2 more
Agent

146 unresolved, 38 unassigned. Top 10 by users: 4 real bugs (assign to Payments and Search), 3 already fixed in 2.3.1 (resolve), 3 noise from a crawler user agent (ignore, and add an inbound filter). Apply these 10?

The SKILL.md file

View raw
name: sentry-issue-triage

Triage a Sentry project's unresolved issues by ranking them by user impact, grouping likely duplicates, and proposing assign, resolve or ignore for each, with approval before changes. Use when the user asks to clean up, triage or prioritise Sentry issues or reduce Sentry noise.

Steps

  1. Resolve the project with find_projects. List the backlog with find_issues, for example is:unresolved is:unassigned, sorted by users affected.
  2. Skim each of the top issues with get_issue_details, enough to tell a real bug from noise such as browser extensions, bots, or network errors the user cannot act on.
  3. Group issues that share a culprit or message pattern; they are often one bug.
  4. Propose one action per issue:
    • Assign, to a team from find_teams or a person, when ownership is clear.
    • Resolve in the next release, when the fix already shipped.
    • Ignore until it escalates, for known noise, with the reason.
    • Investigate, for real impact with an unknown cause.
  5. Suggest inbound filters or a fix to the SDK configuration for repeated noise, with search_docs for the setting.

Apply

Show the table: issue, users, events, proposed action and reason. Make only the approved changes with update_issue, and wait for the user's yes before touching any issue.

Sentry tools it uses

  • find_projects
  • find_issues
  • get_issue_details
  • find_teams
  • search_docs
  • update_issueAsks first

Tool list from Sentry MCP documentation.

FAQ

Will it ignore real errors?

It only proposes ignoring issues it can explain as noise, gives the reason, and changes nothing until you approve.

How does it rank issues?

By users affected first, then event volume and how recent they are.