Fähigkeiten fix-sentry-issues
📦

fix-sentry-issues

Inhaltsrevision r1 Mittleres Risiko ⚙️ Externe Befehle🌐 Netzwerkzugriff

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.

Unterstützt: Claude Codex Code(CC)
Maintain this Skill? Claim it 📊 70 Angemessen

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/brianlovin-fix-sentry-issues.md Signiertes manifest GET /api/skills/brianlovin-fix-sentry-issues/manifest Signiertes lockfile GET /api/skills/brianlovin-fix-sentry-issues/lockfile

Testen

„fix-sentry-issues“ wird verwendet. Triage unresolved checkout issues without changing their status.

Erwartetes Ergebnis:

  • 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“ wird verwendet. Investigate API-77 and explain the root cause.

Erwartetes Ergebnis:

API-77 receives binary document URLs on a text extraction path. Input classification is missing before the external extraction request.

„fix-sentry-issues“ wird verwendet. Prepare a fix summary for a merged timeout issue.

Erwartetes Ergebnis:

Root cause: oversized inputs reached a synchronous parser. Fix: reject unsupported sizes upstream and cover the production failure shape with a sanitized regression test.

Sicherheitsaudit

Mittleres Risiko
v1 • 21.8.2026 Versionsbericht öffnen

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
Gescannte Dateien
73
Analysierte Zeilen
3
Prüfelemente
0
Falschmeldungen ignoriert

Bestätigte Sicherheitsbedenken (1)

Mittel
SKILL.md:54SKILL.md:69
Production Data Reuse Without Redaction
The workflow directs agents to reproduce failures and create tests with actual Sentry inputs without requiring secret or personal-data redaction.
The instructions explicitly require actual production inputs in reproduction and tests. Sentry events can contain sensitive values, while no redaction step is specified.
Elemente der Fähigkeitsprüfung (3)

Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.

Mittel
SKILL.md:48
Ruby/shell backtick execution
2. **Cross-reference Axiom** — Events have `traceId`. `axiom query "['shiori-events'] | where traceI
The line explicitly directs the agent to run the Axiom CLI through a shell command. It interpolates a trace identifier and contacts an external logging service.
Mittel
SKILL.md:67
Ruby/shell backtick execution
One branch per issue. `git checkout main && git pull && git checkout -b fix/<descriptive-name>`
The line explicitly instructs execution of chained Git shell commands that change branches and pull from a remote. The generated branch placeholder requires validation.
Mittel
SKILL.md:54
Fetch API call
5. **Reproduce** — Use actual failing inputs from Sentry. Call the function with exact data. `fetch(
The workflow explicitly instructs fetching URLs copied from production Sentry events. Unvalidated event-controlled URLs can reach untrusted or private network targets.

Risikofaktoren

⚙️ Externe Befehle (8)
SKILL.md:21 SKILL.md:28 SKILL.md:38 SKILL.md:40 SKILL.md:46 SKILL.md:48 SKILL.md:54 SKILL.md:67
🌐 Netzwerkzugriff (1)
SKILL.md:54
Geprüft von: codex
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/brianlovin-fix-sentry-issues/security.svg)](https://skillstore.io/skills/brianlovin-fix-sentry-issues?utm_source=security_passport_badge)

HTML-Badge

<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>

Einbettungskarte

<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>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

brianlovin. (2026). fix-sentry-issues security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brianlovin-fix-sentry-issues/audits/1

BibTeX-Zitat

@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-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
91
Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

List Issues for Triage 
List unresolved Sentry issues for {project}. Build a triage table with issue ID, event count, action, and evidence. Do not change statuses.
Investigate One Issue 
Investigate Sentry issue {issue_id}. Retrieve event details, identify recurring inputs, follow the stack trace, and explain the likely root cause.
Correlate Event Context 
Correlate Sentry issue {issue_id} with Axiom using its trace identifier. Redact sensitive values and summarize the surrounding request context.
Implement a Verified Fix 
Fix Sentry issue {issue_id} in {repository}. Confirm the root cause first. Add a failing regression test, implement the smallest fix, and verify checks.

Bewährte Praktiken

  • 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.

Vermeiden

  • 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.

Häufig gestellte Fragen

Does this skill require Sentry MCP?
Yes. It uses Sentry MCP to discover projects, search issues, inspect events, and update issue status.
Does it automatically resolve Sentry issues?
No. Resolution should occur only after the fix is merged and verified.
Can it investigate several issues together?
It can triage a queue, but investigation and fixes should proceed one issue at a time.
Is Axiom required?
No. Axiom provides optional trace context when its CLI, dataset, and credentials are available.
How should production event data be handled?
Redact secrets and personal data, minimize retained fields, and use synthetic fixtures when possible.
What should a completed fix include?
Include root-cause evidence, a regression test, the focused code change, passing checks, and a clear pull request summary.

Entwicklerdetails

Lizenz

MIT

Skillstore-Revision

r1

Versionshinweis

Der Autor hat keine Version angegeben.

Repository

https://github.com/brianlovin/agent-config/tree/1a9819ebf3fee811150fc76cbe177ea4e5f747ff/skills/fix-sentry-issues

Ref.

261e670d2c95e3e9eae6d71bbb68527d4f36e8b2

Aktualität der Wartung

21.8.2026

Nutzung

0 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md