Stats
Actions
Tags
From sentry
Investigates recent errors and exceptions in Sentry projects: fetches issues via MCP, analyzes frequency, trends, stack traces, user impact, and suggests fixes for quick triage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sentry:investigate-errorsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
sentry:investigate-errors - Investigate recent errors and exceptions in your Sentry projects
sentry:investigate-errors - Investigate recent errors and exceptions in your Sentry projects
/investigate-errors [arguments]
Investigate recent errors and exceptions in your Sentry projects to identify issues, patterns, and root causes.
This command helps you quickly triage and investigate errors captured by Sentry across your projects.
/investigate-errors [project-name] [timeframe]
User: /investigate-errors my-web-app 24h
Claude: Investigating errors in my-web-app for the last 24 hours...
## Error Investigation Report
### Overview
- **Total Issues**: 12 error issues
- **Total Events**: 347 error events
- **Affected Users**: 89 unique users
- **Time Range**: Last 24 hours
### Top Issues
1. **TypeError: Cannot read property 'id' of undefined**
- Events: 156
- Users: 45
- First Seen: 23h ago
- Last Seen: 12m ago
- Environment: production
- Release: v2.3.1
- Trend: Increasing (spike in last 6 hours)
2. **NetworkError: Failed to fetch user data**
- Events: 89
- Users: 23
- First Seen: 18h ago
- Last Seen: 1h ago
- Environment: production
- Release: v2.3.1
3. **ReferenceError: localStorage is not defined**
- Events: 67
- Users: 34
- First Seen: 22h ago
- Last Seen: 3h ago
- Environment: production, staging
### Key Patterns
- 45% of errors correlate with v2.3.1 deployment 23h ago
- TypeError spike began 6 hours after deployment
- NetworkError appears to be intermittent (API flakiness?)
- localStorage errors isolated to server-side rendering context
### Recommendations
1. **Immediate**: Investigate TypeError in v2.3.1 - likely regression in user data handling
2. **High Priority**: Check API stability for fetch failures
3. **Medium Priority**: Add server-side rendering guards for localStorage access
Would you like me to dive deeper into any specific error?
project-name (optional): Sentry project slugtimeframe (optional): Time range (1h, 24h, 7d, 30d, or custom)/analyze-performance: Investigate performance issues/check-releases: Review recent release health/query-events: Run custom Sentry queriesnpx claudepluginhub thebushidocollective/han --plugin hashi-sentryQueries Sentry errors, triages issues, and checks release health via REST API. Useful for debugging exceptions, investigating crashes, stack traces, and monitoring stability.
Queries Sentry API to list issues, inspect events, and summarize production errors using bundled Python script. Requires SENTRY_AUTH_TOKEN for read-only access.
Analyzes and fixes production issues from Sentry using MCP. Methodically investigates stack traces, breadcrumbs, and traces to identify root causes of errors and exceptions.