
Sentry
Query Sentry issues and generate bug reports from the CLI
What You Can Do
This skill enables you to interact with Sentry programmatically via the command line. Authenticate securely, resolve short issue IDs to full bug reports complete with descriptions and stack traces, and extract event details for debugging and reporting purposes. It streamlines the workflow from issue identification to actionable bug report generation.
Features
configure auth tokens and verify credentials with proper scopes
resolve Sentry short IDs (e.g., PROJECT-123) to full issue details
fetch JSON event data including stack traces, breadcrumbs, and context
compile issue metadata, descriptions, and stack traces into formatted reports
extract numeric issue IDs from Sentry dashboard URLs automatically
query and structure event JSON for analysis and reporting
retrieve issues within authenticated org and project scope
Example Output
Example 1: Issue Lookup
Short ID: MYAPP-456
Resolved Issue: Type Error in checkout flow
Status: Unresolved
Error: "Cannot read property 'total' of undefined"
First Seen: 2024-01-15 09:22:14 UTC
Last Seen: 2024-01-16 14:38:02 UTC
Events: 24 occurrences
Example 2: Stack Trace Extract
File: /app/src/checkout.js:142
Function: calculateTotal()
Error: TypeError
Stack:
at calculateTotal (/app/src/checkout.js:142:15)
at processOrder (/app/src/order.js:58:10)
at submitCheckout (/app/src/index.js:201:5)
What's Included
- SKILL.md: Complete Sentry CLI integration guide and primary workflow documentation
- Authentication template: environment variable setup and token configuration checklist
- Short ID resolution workflow: step-by-step process for converting IDs to bug reports
- jq filter templates: JSON query examples for extracting stack traces and metadata
- Security guidelines: practices for handling auth tokens and avoiding credential exposure
Who It's For
- Backend/Full-stack engineers — debugging production issues and investigating error reports
- DevOps/SRE teams — triaging incidents and analyzing error patterns across environments
- QA engineers — investigating bug reports and correlating errors with test sessions
- Technical leads — reviewing error trends and generating incident reports for stakeholders
Best For
- Retrieving full bug reports from short issue IDs
- Extracting stack traces and event details for root cause analysis
- Automating issue lookup workflows in scripts or CI/CD pipelines
- Correlating error events with user sessions and breadcrumbs
- Generating structured incident reports from Sentry data







