sentry

Correlate Sentry issues with local file paths and Git history.

Updated May 29, 2025
One-click install
npx skills add https://github.com/crozzbite/DnDApp --skill sentry-crozzbite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/crozzbite/DnDApp/tree/main/.agent/skills/sentry
Command: npx skills add https://github.com/crozzbite/DnDApp --skill sentry-crozzbite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proactive error analysis and issue correlation across the SkullRender ecosystem using Sentry, enabling faster root-cause identification and trend detection.

Core Features & Use Cases

  • Correlation First: Link Sentry issues to local file paths and Git history to surface relevant context.
  • Impact & Prioritization: Rank issues by frequency, user impact, and proximity to critical Bones (Security/Core).
  • Contextual Debugging: Use the list_issues and get_event tools to fetch event tags and breadcrumbs before proposing fixes.

Quick Start

Run the Sentry auditing workflow against the current project to surface unresolved issues and cross-reference them with repository history.

Frequently Asked Questions about sentry

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

FAQPage Schema
How do I correlate Sentry issues with local file paths and Git history?

To correlate Sentry issues with local file paths and Git history, you can run an auditing workflow that fetches event tags and breadcrumbs, cross-references them with repository code, and surfaces actionable root causes for quick remediation.

What is the best way to prioritize unresolved Sentry incidents by impact?

The best way to prioritize unresolved Sentry incidents is to rank issues by frequency, user impact, and proximity to critical code areas. This approach surfaces high-impact events for quick remediation across active projects.

How do I use Sentry breadcrumbs and event tags for root-cause identification?

You use Sentry breadcrumbs and event tags for root-cause identification by leveraging the list_issues and get_event tooling to gather event context, cross-referencing that data with your repository code to propose fixes.

Can I audit errors and detect trends across multiple active projects using Sentry?

Yes, you can audit errors and detect trends across multiple active projects using Sentry. The workflow applies issue correlation analysis across active projects and unresolved incidents to surface actionable root causes.

Do I need a local Git repository to propose fixes for Sentry issues?

Yes, you need a local Git repository to propose fixes for Sentry issues effectively. The error auditing workflow links Sentry issues with local file paths and Git history to surface relevant context and propose accurate remediation.