fix-sentry-issues
Fix Sentry Issues with Root-Cause Analysis
Production error queues often hide the upstream defect behind repeated symptoms. This skill uses Sentry evidence and code tracing to guide focused, verified fixes.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "fix-sentry-issues" from https://skillstore.io/skills/brianlovin-fix-sentry-issues.md and its manifest at https://skillstore.io/api/skills/brianlovin-fix-sentry-issues/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「fix-sentry-issues」。 Triage unresolved checkout issues without changing their status.
預期結果:
- Investigate CHECKOUT-42: 118 events affect payment confirmation across three releases.
- Ignore CHECKOUT-19: two browser-extension events contain no application stack frames.
- Next step: inspect event inputs and stack traces for CHECKOUT-42.
正在使用「fix-sentry-issues」。 Investigate API-77 and explain the root cause.
預期結果:
API-77 receives binary document URLs on a text extraction path. Input classification is missing before the external extraction request.
正在使用「fix-sentry-issues」。 Prepare a fix summary for a merged timeout issue.
預期結果:
Root cause: oversized inputs reached a synchronous parser. Fix: reject unsupported sizes upstream and cover the production failure shape with a sanitized regression test.
安全審計
中風險Most backtick detections are Markdown code formatting, not Ruby or shell execution. The skill directs agents to run Axiom and Git commands and fetch production-derived URLs, creating command, network, and data-handling risks. No prompt injection or malicious intent was found.
已確認的安全問題 (1)
能力複核項目 (3)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (8)
🌐 網路存取 (1)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/brianlovin-fix-sentry-issues?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/brianlovin-fix-sentry-issues?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brianlovin-fix-sentry-issues/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/brianlovin-fix-sentry-issues.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
brianlovin. (2026). fix-sentry-issues security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1BibTeX 引用
@techreport{brianlovin-brianlovin-fix-sentry-issues-2026,
author = {brianlovin},
title = {fix-sentry-issues security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "fix-sentry-issues security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "brianlovin"
date-released: "2026-08-21"
url: "https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1"
identifiers:
- type: other
value: "skillstore:brianlovin-fix-sentry-issues:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Triage an Error Backlog
Rank unresolved issues by recurrence and user impact, then identify items requiring investigation.
Debug a Recurring Failure
Trace event inputs, stack frames, and request context to find the upstream application defect.
Prepare Focused Fixes
Create issue-specific branches, regression tests, and pull request summaries with clear root-cause evidence.
試試這些提示
List unresolved Sentry issues for {project}. Build a triage table with issue ID, event count, action, and evidence. Do not change statuses.Investigate Sentry issue {issue_id}. Retrieve event details, identify recurring inputs, follow the stack trace, and explain the likely root cause.Correlate Sentry issue {issue_id} with Axiom using its trace identifier. Redact sensitive values and summarize the surrounding request context.Fix Sentry issue {issue_id} in {repository}. Confirm the root cause first. Add a failing regression test, implement the smallest fix, and verify checks.最佳實務
- Investigate one issue at a time and preserve status codes, stack traces, and original error details.
- Redact secrets and personal data before storing Sentry inputs in tests, logs, or pull requests.
- Validate production-derived URLs before fetching them, and require confirmation for remote status changes.
避免
- Do not classify recurring fallbacks as expected without tracing why the primary path failed.
- Do not combine unrelated Sentry issues in one branch or pull request.
- Do not resolve issues or lower log levels before verifying the root cause and deployed fix.
常見問題
Does this skill require Sentry MCP?
Does it automatically resolve Sentry issues?
Can it investigate several issues together?
Is Axiom required?
How should production event data be handled?
What should a completed fix include?
開發者詳細資訊
作者
brianlovin授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
261e670d2c95e3e9eae6d71bbb68527d4f36e8b2
維護新鮮度
2026/8/21
使用量
0 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md