Compétences fix-sentry-issues

📦

fix-sentry-issues

Name: fix-sentry-issues
Author: brianlovin

Révision du contenu r1 Risque moyen ⚙️ Commandes externes🌐 Accès réseau

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.

Prend en charge: Claude Codex Code(CC)

📊 70 Adéquat

Maintain this Skill? Claim it 📊 70 Adéquat

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/brianlovin-fix-sentry-issues.md manifest signé GET /api/skills/brianlovin-fix-sentry-issues/manifest lockfile signé GET /api/skills/brianlovin-fix-sentry-issues/lockfile

Tester

Utilisation de « fix-sentry-issues ». Triage unresolved checkout issues without changing their status.

Résultat attendu:

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.

Utilisation de « fix-sentry-issues ». Investigate API-77 and explain the root cause.

Résultat attendu:

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

Utilisation de « fix-sentry-issues ». Prepare a fix summary for a merged timeout issue.

Résultat attendu:

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

Audit de sécurité

Risque moyen

v1 • 21/08/2026 Ouvrir le rapport versionné

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.

Fichiers analysés

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Préoccupations de sécurité confirmées (1)

Moyen

SKILL.md:54 SKILL.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.

Éléments d’évaluation des capacités (3)

Il s’agit de capacités locales réelles qui peuvent être attendues pour cette compétence ; elles nécessitent donc un examen, mais ne sont pas comptabilisées comme comportement malveillant confirmé.

Moyen

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.

Moyen

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.

Moyen

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.

Facteurs de risque

⚙️ Commandes externes (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

🌐 Accès réseau (1)

SKILL.md:54

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

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

Badge Markdown

[![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)

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>

Carte intégrable

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

Citations académiques (APA · BibTeX · CFF)

Citation 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/1

Citation BibTeX

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

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

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.

Bonnes pratiques

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.

Éviter

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.

Foire aux questions

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.

Détails du développeur

Auteur

brianlovin

Licence

MIT

Révision Skillstore

Avis de version

L’auteur n’a déclaré aucune version.

Dépôt

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

Réf

261e670d2c95e3e9eae6d71bbb68527d4f36e8b2

Récence de maintenance

21/08/2026

Utilisation

0 téléchargements · 0 vues

Structure de fichiers

📄 SKILL.md