sentry

Fetch and analyze Sentry issues and search logs via the Sentry API.

2.8k|212|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/mitsuhiko/agent-commands --skill sentry-mitsuhiko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry
Source: https://github.com/mitsuhiko/agent-commands/tree/main/skills/sentry
Command: npx skills add https://github.com/mitsuhiko/agent-commands --skill sentry-mitsuhiko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill lets you fetch Sentry issues, the latest events, and search logs directly from the Sentry API, helping you understand errors and context faster.

Core Features & Use Cases

  • Fetch Issue: Retrieve issue details by ID or URL.
  • Fetch Latest Event: Get the most recent event with full stack trace.
  • Search Logs: Query Sentry logs with flexible filters, returning structured results.
  • Output: Formatted summaries ready for reporting.

Quick Start

Use the fetch-issue.js script to load an issue by ID or URL, for example: ./scripts/fetch-issue.js 5765604106 Or a URL: ./scripts/fetch-issue.js https://sentry.io/organizations/sentry/issues/5765604106/ To search logs, run: ./scripts/search-logs.js --org myorg --project backend --period 7d

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 view stack traces?

Fetch Sentry issues by ID or URL using the fetch-issue.js script, which retrieves issue details, stack traces, user impact, environment data, and formatted summaries ready for incident response and debugging workflows.

Can I search and filter Sentry logs across projects and time windows?

Search Sentry logs with the search-logs.js script using flexible filters for organization, project, and time period, returning structured results with events, breadcrumbs, and runtime context across your monitoring data.

What authentication is required to access the Sentry API?

An auth token stored in ~/.sentryclirc is required to authenticate API requests; the Skill reads this configuration automatically to fetch issues and logs without manual credential handling.

What input formats does this Skill support for identifying Sentry issues?

The Skill accepts numeric IDs, full URLs, new format URLs, and short IDs to identify Sentry issues, making it flexible for different workflows—whether you're pasting from the UI or using programmatic identifiers.

How do I get the latest event and full context for a Sentry issue?

Fetch the latest event for an issue to retrieve the most recent occurrence with complete stack trace, requests, breadcrumbs, and runtime context, enabling rapid root-cause analysis and incident response.