triage-frontend-issues

Archives non-actionable noise issues in the Sentry javascript project via Sentry MCP.

974|51|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/getsentry/skills --skill triage-frontend-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-frontend-issues
Source: https://github.com/getsentry/skills/tree/main/skills/triage-frontend-issues
Command: npx skills add https://github.com/getsentry/skills --skill triage-frontend-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The sentry/javascript issue queue accumulates non-actionable noise — third-party library errors, browser API permission denials, test events, and transient backend 5xx — that buries real bugs and wastes triage time.

Core Features & Use Cases

  • Criteria-based classification: Classifies each unresolved issue as archive, skip, or needs-human using a documented taxonomy of nine noise categories with recognition heuristics.
  • Safe archive-only mutations: Only sets status to ignored with untilEscalating mode, always with a category-tagged reason, and never resolves, assigns, or deletes.
  • Confirmation-gated batch plans: Builds a Markdown triage plan table and waits for explicit user approval before calling update_issue on any issue.
  • Use Case: Ask the agent to triage the javascript project; it searches the unresolved queue, classifies up to 50 issues against the archive criteria, presents a plan, and archives only the approved subset.

Quick Start

Ask the agent to triage new frontend issues in the sentry/javascript project and archive the non-actionable ones.

Frequently Asked Questions about triage-frontend-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage issues in the Sentry javascript project?▼

Invoke the skill with no arguments to load the default queue of unresolved, unassigned issues from the last 7 days, or pass an issue URL, short ID, or Sentry search query. The skill classifies each issue and presents a plan for your approval before archiving anything.

What kinds of Sentry issues get archived as noise?▼

Nine categories qualify: single-event flukes, test or synthetic events, wrong-project backend errors, third-party library noise, browser API permission errors, transient backend 5xx, network failures to external hosts, corporate proxy interference, and zero-impact unknown-title issues.

Can this skill resolve or assign Sentry issues?▼

No. The only permitted mutation is setting status to ignored with untilEscalating mode. It never resolves, unresolves, assigns, or deletes issues, and every archive requires a category-tagged reason and explicit user approval.

What happens if an issue might be a real bug?▼

Issues whose top frame is in application code, or that cannot be confidently classified, are marked skip or needs-human and never archived. The skill follows a when-in-doubt-skip rule and surfaces uncertain cases for human review.

What tools does Sentry issue triage require?▼

It requires an authenticated Sentry MCP server providing search_issues, get_sentry_resource, and update_issue. If update_issue is unavailable, the skill stops and asks you to authenticate the Sentry MCP server first.