---
title: "Sentry Frontend Queue Triage: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/getsentry-triage-frontend-issues/
description: "Prepare a bounded archive plan for the Sentry internal javascript issue queue and apply only the approved rows."
---

# Sentry Frontend Queue Triage: review, setup & limitations · Undominated.ai

> Prepare a bounded archive plan for the Sentry internal javascript issue queue and apply only the approved rows.

[← Explore all skills](/skills/)

DEVELOPMENT WORKFLOW / getsentry

# Sentry Frontend Queue Triage

Prepare a bounded archive plan for the Sentry internal javascript issue queue and apply only the approved rows.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher getsentry
 Licence [Apache-2.0 ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE)
 Revision d18b7aa8ba87
 [Read what was—and wasn’t—checked ↓](#review)

“Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", …”

 [getsentry · upstream description ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The skill only archives issues in the sentry/javascript project, and only with untilEscalating, after the user approves the displayed plan.
- Anything that might be a bug in the project's own code is left as needs-human rather than archived.
- The definition enforces project/status/assignee boundaries, per-batch review and category-tagged reasons, with explicit skipped/needs-human outcomes.
- Separate actionable application bugs from confidently classified environment noise

### A good fit for

 - Clearing non-actionable noise from the sentry/javascript unresolved queue.
- Stopping when the request names a different Sentry project.
- Separate actionable application bugs from confidently classified environment noise
- Archive with escalation enabled while preserving uncertain issues for human review
- Report individual archive failures while preserving the approved issue subset and plan.

### Weigh up before choosing

 - It needs the Sentry MCP at mcp.sentry.dev and the update_issue tool. If that tool is missing it stops.
- A single approval covers only the plan on screen. It does not resolve issues and it does not use forever or a count-based ignore.
- This review did not execute the resource.
- This definition is specifically scoped to organization sentry and project javascript; it is not a generic drop-in for another account.
- Third-party frames, age or event volume alone do not establish non-actionability; ambiguous cases remain skipped or needs-human.
- It archives rather than resolves and does not automatically reverse an archive; permission to inspect is distinct from approval of the displayed archive plan.
- An approval covers only the displayed plan; changed plans need renewed confirmation, and mistaken archives are left for the user to reverse in Sentry.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/triage-frontend-issues/SKILL.md
- skills/triage-frontend-issues/references/archive-criteria.md
- LICENSE
- README.md

### Our findings

 - Calls go to mcp.sentry.dev. The organisation and project are fixed as sentry and javascript. A different project stops the skill.
- The only write is status=ignored with ignoreMode=untilEscalating, and only after an explicit approval of that batch.
- Archive criteria require a matching noise category. A plausible bug in project code is not archived, and already resolved or ignored issues are skipped.
- The definition enforces project/status/assignee boundaries, per-batch review and category-tagged reasons, with explicit skipped/needs-human outcomes.
- The apply step performs status updates sequentially, records failures per issue, and rebuilds the plan after edits instead of assuming the prior approval still applies.

### Not established by this review

 - The resource was not executed and its tools were not called.
- The Sentry MCP was not called and no issue was updated.
- No skill execution, authenticated service operation, or outcome benchmark was performed.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/README.md)

DOCUMENTED COMMAND

 npx skills add getsentry/skills/skills/triage-frontend-issues Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues Copy reviewed-revision command ↗ - Install the pinned skill directory interactively, retaining its bundled references and scripts.
- Authenticate the Sentry MCP tools and inspect issue details beyond the search summary.
- Produce the category/reason table, obtain approval for that exact set and apply sequential untilEscalating updates with a failure report.

### Before you start

 - Authorized access to the named internal Sentry project
- Sentry MCP search_issues, get_sentry_resource and update_issue

### Compatibility

Agents supporting directory-based SKILL.md instructions

### Local instructions; runtime access depends on the workflow

 - Read potentially sensitive issue/event metadata and mutate issue status to ignored with escalation enabled for an approved set.

### Cost model

The skill is free; service usage and infrastructure can incur charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned skill definition ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md Supports: summary, whySelected, bestFor, limitations, install, access, review
- [Publisher repository and installation guidance ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/README.md) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/README.md Supports: install
- [Apache-2.0 licence ↗](https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE) Checked 2026-10-14 https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE Supports: license
- [Pinned continuation review W08 ↗](https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md Supports: review.findings, bestFor, limitations, upstreamDescription

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Evidence-Based Skill Writing ↗ Choose a skill structure, preserve source adaptation decisions and iterate against working and holdout examples.](/skills/getsentry-skill-writer/)[### Iterate on Pull Requests ↗ Resolve actionable CI failures and review feedback while reporting human merge gates separately.](/skills/getsentry-iterate-pr/)[### Reviewer-Facing PR Writing ↗ Write or refresh PR titles and bodies from the full branch change and its reviewer impact.](/skills/getsentry-pr-writer/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
