Навыки fix-sentry-issues

📦

fix-sentry-issues

Name: fix-sentry-issues
Author: brianlovin

Ревизия содержимого r1 Средний риск ⚙️ Внешние команды🌐 Доступ к сети

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.

Поддерживает: Claude Codex Code(CC)

📊 70 Адекватно

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу 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.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/brianlovin-fix-sentry-issues.md Подписанный manifest GET /api/skills/brianlovin-fix-sentry-issues/manifest Подписанный lockfile GET /api/skills/brianlovin-fix-sentry-issues/lockfile

Протестировать

Использование «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.

Аудит безопасности

Средний риск

v1 • 21.08.2026 Открыть версионный отчет

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)

Средний

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.

Пункты проверки возможностей (3)

Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.

Средний

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.

Средний

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.

Средний

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.

Факторы риска

⚙️ Внешние команды (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

🌐 Доступ к сети (1)

SKILL.md:54

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

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

Значок 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)

Значок 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/1

Цитата 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"

Оценка 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 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.

Лучшие практики

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?

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.

Сведения для разработчиков

Автор

brianlovin

Лицензия

MIT

Ревизия Skillstore

Примечание о версии

Автор не указал версию.

Репозиторий

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

Ссылка

261e670d2c95e3e9eae6d71bbb68527d4f36e8b2

Актуальность поддержки

21.08.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📄 SKILL.md