Fetch and analyze Sentry issues and search logs directly from the API. Helps agents understand errors, stack traces, logs, and issue context.
The Sentry skill allows users to fetch and analyze issues, events, transactions, and logs from Sentry's platform for error debugging and root cause analysis. It leverages an authentication token from `~/.sentryclirc` to access the data, providing agents with a robust tool to investigate and resolve application errors. This skill is essential for understanding what happened at specific times, helping teams quickly identify problems and take corrective actions to ensure smooth operations.
This skill provides multiple commands for interacting with Sentry data, such as searching events by time range, listing open issues, fetching specific issue or event details, and even searching logs based on criteria like error level or custom tags. The Sentry skill is capable of displaying detailed stack traces, breadcrumbs, user impact, and other contextual information necessary for efficient debugging. It also supports searching events using various parameters such as project and user-related data, enabling users to narrow down issues precisely.
Target users include developers, system administrators, and support agents who rely on Sentry for error monitoring and troubleshooting. By enabling quick and in-depth access to Sentry’s data, this skill is ideal for debugging complex issues, finding high-frequency errors, and investigating specific events or transactions that may have impacted user experiences.
You can use the `search-events.js` command with the `--start` option to specify the date and time, for example, `search-events.js --org <org> --start 2025-12-23T15:00:00 --level error`.
Yes, use the `fetch-issue.js` or `fetch-event.js` commands to get full details. For example, `fetch-issue.js <issue-id> --latest` will fetch the latest details for a specific issue.
This skill requires an authentication token from your `~/.sentryclirc` file and the Sentry organization and project information to access the data.
Yes, you can search events using custom tags by using the `--tag` option, for example, `search-events.js --org <org> --tag thread_id:th_abc123`.
Events are limited to the scope and time range you specify in your query. You can adjust the time period using options like `--period`, `--start`, and `--end` to focus on the relevant timeframe.
Quick Setup:
.claude/skills/Repository
mitsuhiko/agent-commands