Sentry Fix Issues
- 5 installs
- 12 repo stars
- Updated July 13, 2026
- getsentry/webvitals.com
sentry-fix-issues skill documents Find and fix issues from Sentry using MCP.
About
sentry-fix-issues skill documents Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.. name: sentry-fix-issues description: Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.
- Find and fix issues from Sentry using MCP.
- Platform-specific setup patterns for sentry-fix-issues.
- Evidence-backed steps from upstream SKILL.md.
- When-to-use criteria for sentry-fix-issues versus alternatives.
Sentry Fix Issues by the numbers
- 5 all-time installs (skills.sh)
- Ranked #881 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Jul 24, 2026 (Skillselion catalog sync)
sentry-fix-issues capabilities & compatibility
- Capabilities
- sentry fix issues quick start · sentry fix issues when to use guidance · sentry fix issues integration patterns
- Works with
- sentry
- Use cases
- code review
What sentry-fix-issues says it does
Discover, analyze, and fix production issues using Sentry's full debugging capabilities.
User asks to "fix Sentry issues" or "resolve Sentry errors"
npx skills add https://github.com/getsentry/webvitals.com --skill sentry-fix-issuesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 12 |
| Last updated | July 13, 2026 |
| Repository | getsentry/webvitals.com ↗ |
How do I use sentry-fix-issues correctly?
Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces,
Who is it for?
Teams implementing sentry-fix-issues workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about sentry-fix-issues, find and fix issues from sentry using mcp. use when asked to fix sentry errors, debug prod.
What you get
Working sentry-fix-issues setup with validated configuration and next steps.
Files
Fix Sentry Issues
Discover, analyze, and fix production issues using Sentry's full debugging capabilities.
Invoke This Skill When
- User asks to "fix Sentry issues" or "resolve Sentry errors"
- User wants to "debug production bugs" or "investigate exceptions"
- User mentions issue IDs, error messages, or asks about recent failures
- User wants to triage or work through their Sentry backlog
Prerequisites
- Sentry MCP server configured and connected
- Access to the Sentry project/organization
Phase 1: Issue Discovery
Use Sentry MCP to find issues. Confirm with user which issue(s) to fix before proceeding.
| Search Type | MCP Call |
|---|---|
| Recent unresolved | sentry_search_issues query: "is:unresolved" sort: "date" |
| Specific error type | sentry_search_issues query: "is:unresolved error.type:TypeError" |
| By ID | sentry_get_issue issue_id: "PROJECT-123" |
Phase 2: Deep Issue Analysis
Gather ALL available context for each issue:
| Data Source | MCP Call | Extract |
|---|---|---|
| Core Error | sentry_get_issue | Exception type/message, full stack trace, file paths, line numbers, function names |
| Event Details | sentry_get_event | Breadcrumbs, tags, custom context, request data |
| Trace (if available) | sentry_get_trace | Parent transaction, spans, DB queries, API calls, error location |
| Replay (if available) | sentry_get_replay | User actions, UI state, network requests |
Phase 3: Root Cause Hypothesis
Before touching code, document:
1. Error Summary: One sentence describing what went wrong 2. Immediate Cause: The direct code path that threw 3. Root Cause Hypothesis: Why the code reached this state 4. Supporting Evidence: Breadcrumbs, traces, or context supporting this 5. Alternative Hypotheses: What else could explain this? Why is yours more likely?
Challenge yourself: Is this a symptom of a deeper issue? Check for similar errors elsewhere, related issues, or upstream failures in traces.
Phase 4: Code Investigation
| Step | Actions |
|---|---|
| Locate Code | Read every file in stack trace from top down |
| Trace Data Flow | Find value origins, transformations, assumptions, validations |
| Error Boundaries | Check for try/catch - why didn't it handle this case? |
| Related Code | Find similar patterns, check tests, review recent commits (git log, git blame) |
Phase 5: Implement Fix
Before writing code, confirm your fix will:
- [ ] Handle the specific case that caused the error
- [ ] Not break existing functionality
- [ ] Handle edge cases (null, undefined, empty, malformed)
- [ ] Provide meaningful error messages
- [ ] Be consistent with codebase patterns
Apply the fix: Prefer input validation > try/catch, graceful degradation > hard failures, specific > generic handling, root cause > symptom fixes.
Add tests reproducing exact Sentry event conditions and verifying edge cases.
Phase 6: Verification Audit
Complete before declaring fixed:
| Check | Questions |
|---|---|
| Evidence | Does fix address exact error message? Handle data state shown? Prevent ALL events? |
| Regression | Could fix break existing functionality? Other code paths affected? Backward compatible? |
| Completeness | Similar patterns elsewhere? Related Sentry issues? Add monitoring/logging? |
| Self-Challenge | Root cause or symptom? Considered all event data? Will handle if occurs again? |
Phase 7: Report Results
Format:
## Fixed: [ISSUE_ID] - [Error Type]
- Error: [message], Frequency: [X events, Y users], First/Last: [dates]
- Root Cause: [one paragraph]
- Evidence: Stack trace [key frames], breadcrumbs [actions], context [data]
- Fix: File(s) [paths], Change [description]
- Verification: [ ] Exact condition [ ] Edge cases [ ] No regressions [ ] Tests [y/n]
- Follow-up: [additional issues, monitoring, related code]Quick Reference
MCP Tools: sentry_search_issues, sentry_get_issue, sentry_get_event, sentry_get_trace, sentry_get_replay, sentry_list_projects, sentry_get_project
Common Patterns: TypeError (check data flow, API responses, race conditions) • Promise Rejection (trace async, error boundaries) • Network Error (breadcrumbs, CORS, timeouts) • ChunkLoadError (deployment, caching, splitting) • Rate Limit (trace patterns, throttling) • Memory/Performance (trace spans, N+1 queries)
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
What does sentry-fix-issues do?
sentry-fix-issues skill documents Find and fix issues from Sentry using MCP.
When should I use sentry-fix-issues?
User asks about sentry-fix-issues, find and fix issues from sentry using mcp. use when asked to fix sentry errors, debug prod.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.