debugging-with-sentry

Analyze Sentry events to debug user-reported production issues.

Updated Aug 23, 2026

Search Tags:#observability #sentry #bug investigation #event analysis #production debugging

Ready to run

npx skills add https://github.com/B4rz99/fidy --skill debugging-with-sentry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-with-sentry
Source: https://github.com/B4rz99/fidy/tree/main/.agents/skills/debugging-with-sentry
Command: npx skills add https://github.com/B4rz99/fidy --skill debugging-with-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a streamlined approach to debugging user-reported bugs and production issues using Sentry, the primary observability tool for the application.

Core Features & Use Cases

Event Analysis: Analyze Sentry events for duplicate transactions, missing data, and sync issues.
Quick Reference: Access a guide to Sentry events, including pipeline events and warnings.
Debugging Playbook: Follow a structured approach to common problems like duplicate transactions and data sync issues.
User Identity Tracking: Trace events back to individual users for personalized debugging.
Sentry Access: Utilize Sentry tools for querying issues, events, and user trails.

Quick Start

Use the debugging-with-sentry skill to investigate a reported issue by checking Sentry for the user's event trail.

Frequently Asked Questions about debugging-with-sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate user-reported bugs using Sentry events?▼

You can investigate user-reported bugs using Sentry events by tracing the user's event trail to identify production issues. This involves analyzing pipeline events, checking for missing data, and filtering events to isolate the root cause of the reported bug.

What is the best way to debug duplicate transactions in production?▼

The best way to debug duplicate transactions in production is to follow a structured debugging playbook that analyzes Sentry events. By querying Sentry issues and tracing user identity, you can isolate and resolve the sync issues causing the duplicates.

How does Sentry event analysis work for tracking user identity?▼

Sentry event analysis works for tracking user identity by tracing events back to individual users for personalized debugging. This allows you to query a specific user's event trail to find missing data or sync issues tied to their production issues.

Do I need Sentry access to investigate production issues with this approach?▼

Yes, you need Sentry access to investigate production issues with this approach. The debugging process requires the ability to query issues, filter events, and interpret pipeline warnings directly within the Sentry observability tool.

Can I use Sentry to find missing data and sync issues in pipeline events?▼

Yes, you can use Sentry to find missing data and sync issues in pipeline events. The event analysis process involves accessing a quick reference guide to interpret pipeline events and warnings to identify data inconsistencies.

Why does my Sentry event trail show data sync issues?▼

Your Sentry event trail shows data sync issues when pipeline events fail to align correctly during processing. By applying a structured debugging playbook, you can analyze these Sentry events to identify the exact point of failure and resolve the missing data.