sentry

Fetch and analyze Sentry issues, events, transactions, and logs via the Sentry API.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill sentry-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/sentry
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill sentry-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Sentry issues, events, transactions, and logs can be difficult to track across teams; this Skill helps you fetch, summarize, and analyze them to identify root causes quickly.

Core Features & Use Cases

  • Fetch latest issues, events, and logs from a given organization and project.
  • Surface patterns, failures, and performance anomalies for debugging.
  • Use case: when error rates spike, pull related events and breadcrumbs to trace root causes.

Quick Start

Ask the system to fetch and display the latest Sentry issues, events, or logs for a given org and project to begin debugging.

Frequently Asked Questions about sentry

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

FAQPage Schema
How do I fetch Sentry issues and events for root-cause analysis?

Fetch Sentry issues and events for root-cause analysis by querying a specific organization and project using the Sentry API. The skill retrieves issue details, events, logs, and stack traces to help trace errors and identify the root cause quickly.

Can I query Sentry logs and transactions by date and project?

Yes, you can query Sentry logs and transactions by date, project, and organization. The skill uses Sentry API endpoints to fetch the requested data, returning either formatted text or raw JSON for your debugging workflows.

Do I need a sentryclirc auth token to investigate Sentry error rates?

Yes, you need a valid ~/.sentryclirc auth token to investigate Sentry error rates. This token is required to authenticate with the Sentry API endpoints when fetching issues, events, and logs for your debugging workflow.

What is the best way to surface patterns from Sentry stack traces?

The best way to surface patterns from Sentry stack traces is to pull related events and breadcrumbs through the Sentry API. This allows you to identify failures, performance anomalies, and root causes across your projects.

Does this approach return raw JSON or formatted text for Sentry logs?

Querying Sentry logs through this approach returns either formatted text or raw JSON. You can use these outputs to analyze stack traces, events, and issue details directly within your debugging workflow.

Why should I fetch Sentry events instead of just viewing the dashboard?

Fetching Sentry events programmatically surfaces related logs, breadcrumbs, and stack traces in one place. This helps you track patterns, failures, and performance anomalies across teams more effectively than the dashboard alone for root-cause analysis.