Triage Frontend Issues
SentryOfficialPublished by Sentry
- Skill
- Workflow
- Software development
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, safe workflow for triaging the Sentry javascript project issue queue. It identifies non-actionable noise—such as third-party library errors, browser permission issues, or synthetic test traffic—and allows users to archive these items in bulk using the 'untilEscalating' ignore mode. The process emphasizes safety by requiring explicit user confirmation for all actions, strictly limiting operations to the 'javascript' project, and defaulting to skipping any issue that could potentially be a valid bug.
What it does
- Searches and retrieves unresolved issues from the Sentry javascript project.
- Classifies issues based on documented criteria like third-party noise, flukes, or synthetic traffic.
- Generates a clear, tabular triage plan for user review.
- Executes bulk archiving of approved issues using the untilEscalating ignore mode.
- Provides a summary report of all actions taken, including any failures.
- Ensures safety by requiring explicit user approval before any status changes occur.
When to use it
- When the Sentry javascript issue queue is cluttered with non-actionable noise.
- When you need to quickly filter out known patterns like browser extension errors or third-party library flukes.
- When you want to maintain a clean, actionable backlog for the frontend team.
- When you need to perform routine maintenance on the issue queue without accidentally resolving valid bugs.
Advantages
- Reduces manual effort in cleaning up high-volume, low-signal issue queues.
- Maintains high safety standards by requiring human confirmation for all changes.
- Prevents accidental resolution of valid bugs by defaulting to skip.
- Standardizes the reasoning for archived issues, improving team transparency.
- Strictly enforces project scope to prevent accidental cross-project interference.
Usage examples
- “Triage the javascript project.”
- The agent fetches the default queue of unresolved issues, classifies them, and presents a markdown table for your approval to archive the noise.
- “Archive non-actionable issues in sentry/javascript.”
- The agent scans the queue, identifies issues matching the archive criteria, and asks for confirmation to apply the 'untilEscalating' status to the identified items.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/getsentry/triage-frontend-issues/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip triage-frontend-issues.zip -d .agents/skills
Documentation by Sentry
Triage Frontend Issues
Archive non-actionable noise from the sentry/javascript issue queue: only archive, always untilEscalating, always with a stated reason. Issues that look actionable in our code, or that you cannot confidently classify, must be skipped.
Hard Rules
These rules override anything else. Do not relax them.
Project scope. Only operate on
organizationSlug=sentry, project slugjavascript. If asked to triage a different project, stop and ask the user to confirm.Archive only. The only status mutation permitted is
status=ignored. Never resolve, never unresolve, never assign, never delete, never bulk-update fields other than status.Always
untilEscalating. UseignoreMode=untilEscalating. Never useforever,forDuration,untilOccurrenceCount, oruntilUserCount. If the user asks for a different mode, stop and have them archive that issue manually — this skill does not perform non-escalating archives.Always include a
reason. Thereasonmust be a short, factual sentence naming the category fromreferences/archive-criteria.md(e.g., "Third-party library noise — echarts internals; not actionable in our code").Never touch issues outside the unresolved queue. Skip anything with
statusofresolved,ignored, orreprocessing.Never archive without confirmation. Build a full plan, show it to the user, wait for explicit approval before calling
update_issue. A single approval covers the displayed plan only; new batches need new approval.When in doubt, skip. If an issue could plausibly be a real bug in our code, do not archive it. Surface it as
needs-humanin the plan with a one-line note.
Prerequisites
Sentry MCP authenticated via
mcp.sentry.dev. Required tools:search_issues,get_sentry_resource,update_issue.If
update_issueis not available, stop and ask the user to authenticate the Sentry MCP server.
Inputs
$ARGUMENTS is one of:
| Input shape | Meaning |
|---|---|
Sentry issue URL (https://sentry.sentry.io/issues/JAVASCRIPT-…) | Triage that single issue. |
Issue short ID (JAVASCRIPT-…) | Triage that single issue. |
Sentry issue query (contains a colon, e.g. is:unresolved firstSeen:-24h) | Use as the search query. |
| Empty | Use the default triage queue: is:unresolved is:unassigned firstSeen:-7d, sort new, limit 50. |
If $ARGUMENTS is ambiguous, ask the user to clarify before searching.
Workflow
1. Load the queue
For single-issue input:
Call
get_sentry_resource(url=<issue-url>)orget_sentry_resource(resourceType='issue', organizationSlug='sentry', resourceId=<shortId>).Confirm
Projectis the javascript frontend project. If not, stop.
For query/default input:
Call
search_issues(organizationSlug='sentry', projectSlugOrId='javascript', query=<query>, sort='new', limit=50).Then call
get_sentry_resourcefor each result in parallel to get culprit, substatus, assignee, and stack-frame hints (the search response omits some fields).
Skip immediately if any of these are true on an issue:
statusis notunresolved(already archived, resolved, or in reprocessing).assignedTois set to a human (someone is already owning it).assignedTois set to a team other thanfrontend/issuesand the issue looks team-specific (let the owning team triage).
2. Classify each issue
Read references/archive-criteria.md for the category taxonomy with recognition heuristics and examples. For each candidate issue, produce one of:
| Decision | Meaning |
|---|---|
archive | Matches a documented category; include the category name in the reason. |
skip | Could be a real bug in our code, or insufficient evidence; do not archive. |
needs-human | Looks like noise but doesn't cleanly fit a category, or volume is unusually high; flag for user review. |
When evaluating, weight these signals (in this order):
Top non-Sentry-SDK frame. If the top in-app frame is in
node_modules/,chrome-extension://, a third-party host, or<unknown>, this is a strong archive signal.Title pattern. Many archives are recognizable from the title alone (see criteria reference).
Volume is not a veto. Some high-volume issues (10k+ events, thousands of users) are still archive-worthy if the top frame is third-party. Volume alone never forces archive either.
Recency. Single-event issues older than 30 days with no recurrence are usually noise.
Customer org spread. If events come from one customer subdomain only (check
customerDomain.subdomaintag), it is likely customer-environment noise.
3. Build the plan
Output one Markdown table to the user, in this exact shape:
## Triage plan — sentry/javascript (<N> candidates)
| # | Issue | Title | Volume | Decision | Category | Reason |
|---|-------|-------|--------|----------|----------|--------|
| 1 | [JAVASCRIPT-XXXX](url) | TypeError: ... | 12e/3u | archive | browser-api-noise | Browser clipboard permission denied; not actionable. |
| 2 | [JAVASCRIPT-YYYY](url) | <unknown> | 4945e/123u | needs-human | — | High volume, no title — please review before archiving. |
| 3 | [JAVASCRIPT-ZZZZ](url) | ZodError: ... | 360e/132u | skip | — | Schema validation failure in our code; looks actionable. |Then summarize counts: N archive / M skip / K needs-human. End with:
Reply `apply` to archive the N issues marked `archive`, `apply N,M,...` to archive a subset, or `cancel` to take no action.4. Apply on approval
When the user replies apply (or apply <subset>):
For each issue in the approved set, call:
update_issue(
organizationSlug='sentry',
issueId=<shortId>,
status='ignored',
ignoreMode='untilEscalating',
reason=<category-tagged reason from the plan>,
)Run these sequentially (not in parallel). If a call fails, log the failure, continue with the remaining issues, and report the failed IDs in step 5.
If the user replies cancel or asks to modify the plan, do NOT call update_issue. If they reply with edits ("change row 2 to skip"), rebuild the plan and re-confirm.
5. Report
After applying, output:
## Triage report
- Archived: N
- Skipped: M
- Needs human review: K
- Failures: F (with issue IDs)
<details><summary>Archived issues</summary>
- JAVASCRIPT-XXXX — <reason>
- ...
</details>Recovery
If
update_issuefails on one item, log the failure and continue with the rest. Report failed IDs at the end.If the user notices a wrong archive, the user can unarchive it themselves in Sentry. The skill never reverses its own actions automatically.
If the user asks "redo the plan with these tweaks" mid-flow, regenerate the plan from scratch — do not assume the previous plan still applies.
Example reasons (use this voice)
Third-party library noise — echarts tooltip; not actionable in our code.Browser API permission noise — Clipboard writeText denied by user agent.Customer-environment proxy interference — 200 response treated as error (HTML body from corporate proxy).Transient backend 5xx — InternalServerError on /api/0/organizations/.../events-meta/; backend transient.Test/synthetic event — smoke test or security probe, not production traffic.Wrong project — Prisma/Python error mis-routed to frontend project.Single-event fluke — 1 event, 1 user, no recurrence in 30+ days.Browser extension noise — ReferenceError for extension-injected global (DarkReader/WeixinJSBridge).
Files
- ATTRIBUTION.mdAdded by AutoGineer868 B
- LICENSELicence file added by AutoGineer10.5 KiB
- SKILL.md8.0 KiB
- SPEC.md4.4 KiB
- references/archive-criteria.md9.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Copyright 2025 Functional Software, Inc. dba Sentry
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools, Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Sentry
- Publisher
- Sentry (Official)
- Source
- getsentry/skills · skills/triage-frontend-issues · commit e94f222
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Sentry or Sentry.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download triage-frontend-issues.zip