← Explore all 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.

“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", …”

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

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 ↗

DOCUMENTED COMMAND

npx skills add getsentry/skills/skills/triage-frontend-issues

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
  1. Install the pinned skill directory interactively, retaining its bundled references and scripts.
  2. Authenticate the Sentry MCP tools and inspect issue details beyond the search summary.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. Pinned skill definition ↗Checked

    https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md

    Supports: summary, whySelected, bestFor, limitations, install, access, review

  2. https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/README.md

    Supports: install

  3. Apache-2.0 licence ↗Checked

    https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE

    Supports: license

  4. https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/triage-frontend-issues/SKILL.md

    Supports: review.findings, bestFor, limitations, upstreamDescription

Evidence & Ask