المهارات fix-sentry-issues
📦

fix-sentry-issues

مراجعة المحتوى 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 كافٍ

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل
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 عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو 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 • ٢١‏/٨‏/٢٠٢٦ فتح التقرير المرتبط بالإصدار

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
الملفات التي تم فحصها
73
الأسطر التي تم تحليلها
3
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة

مخاوف أمنية مؤكدة (1)

متوسط
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.
عناصر مراجعة القدرات (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 الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار
تقييم الأمان

نسخ رابط التقرير

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

سبب هذا التقييم موثوقية الأدلة: متوسط
55
الهندسة المعمارية
85
قابلية الصيانة
87
المحتوى
65
المجتمع
91
الامتثال للمواصفات

ما الذي يمكنك بناؤه

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

r1

تنبيه الإصدار

لم يعلن المؤلف عن إصدار.

المستودع

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

مرجع

261e670d2c95e3e9eae6d71bbb68527d4f36e8b2

حداثة الصيانة

٢١‏/٨‏/٢٠٢٦

الاستخدام

0 تنزيلات · 0 مشاهدات

بنية الملفات

📄 SKILL.md

المزيد من brianlovin

عرض الكل

مهارات ذات صلة

عرض الكل
📦

appinsights-instrumentation

84

تجهيز تطبيقات Azure باستخدام Application Insights

بواسطة microsoft

قد تكون إضافة بيانات قياس موثوقة إلى التطبيقات المستضافة على Azure صعبة عبر أطر العمل ونماذج النشر المختلفة. توفر هذه المهارة إرشادات موجزة لإعداد Application Insights، ومراجع SDK، وأنماط تكوين Azure.

DevOps والبنية التحتية عرض