Fix Sentry Issues
- 11 installs
- 356 repo stars
- Updated March 25, 2026
- brianlovin/agent-config
fix-sentry-issues is a Claude skill that uses the Sentry MCP to discover, triage, and root-cause fix production issues one at a time.
About
fix-sentry-issues is a workflow for discovering, triaging, and fixing production errors using the Sentry MCP server. It treats each error as a signal, builds an Investigate-or-Ignore triage table, then investigates one issue at a time by pulling event data, reading the failing code path, tracing inputs upstream, and reproducing. It fixes the root cause on a per-issue branch and resolves the Sentry issue only after merge.
- Uses the Sentry MCP to discover, triage, and root-cause production issues
- Enforces a triage table with only Investigate or Ignore actions before any fix
- Rejects log-level suppression as a fix and traces the input path upstream to the real cause
Fix Sentry Issues by the numbers
- 11 all-time installs (skills.sh)
- Ranked #418 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
fix-sentry-issues capabilities & compatibility
Free skill; requires a Sentry MCP server and Sentry account access
- Capabilities
- error triage · root cause analysis · production debugging · issue resolution
- Works with
- sentry · github
- Use cases
- debugging
- Pricing
- Free
What fix-sentry-issues says it does
**The Sentry error is not the problem. It's a signal.**
Build a triage table. Action = **Investigate** or **Ignore** only:
One branch per issue.
npx skills add https://github.com/brianlovin/agent-config --skill fix-sentry-issuesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 11 |
|---|---|
| repo stars | ★ 356 |
| Last updated | March 25, 2026 |
| Repository | brianlovin/agent-config ↗ |
What it does
Triage and root-cause fix production errors surfaced in Sentry, one issue at a time, addressing the underlying defect.
Who is it for?
Root-cause triage and fixing of production errors reported in Sentry
Skip if: Suppressing errors by downgrading log levels without investigation
When should I use this skill?
You are asked to fix Sentry issues, triage production errors, or investigate an error spike
What you get
Each investigated issue is root-caused, fixed on its own branch, and resolved in Sentry after merge.
- Triage table
- Root-cause analysis per issue
- Per-issue fix branch and PR
By the numbers
- 3 phases: Discover & Triage, Investigate, Fix
- 6 investigation steps
Files
Fix Sentry Issues
Philosophy
The Sentry error is not the problem. It's a signal.
Your goal is not to close the Sentry issue. Your goal is to discover the root cause, understand what's wrong with the application, and fix the underlying defect. Closing the Sentry issue is a side effect of doing that correctly.
Ask "Why does this fail?" — not "How do I make Sentry quiet?" Never treat log level changes as fixes. A fallback path means degraded user experience; trace why the primary path fails and fix it upstream.
Anti-patterns (do not do these)
- Batch-classifying as "expected" without investigation. Seeing a fallback does NOT mean you understand the failure. Trace the full input path.
- Treating "has a fallback" as "not a problem." Why does the primary path fail? Can we prevent it upstream?
- Combining multiple issues into one PR. Each has its own root cause. Fix individually (except when investigation proves identical cause).
- Throwing away error details. Never remove
errorfromcatch (error)or strip status codes. That data is how you understand failures. - Deciding the fix during triage. Classify as "Investigate" or "Ignore" only. You don't know the fix until investigation is complete.
Log level downgrade is valid ONLY for genuinely expected states (e.g., optional column missing, resource deleted) — NOT for failures with fallbacks.
Phase 1: Discover & Triage
Use Sentry MCP (ToolSearch first to load tools): find_organizations → find_projects → search_issues with naturalLanguageQuery: "all unresolved issues sorted by events".
Build a triage table. Action = Investigate or Ignore only:
| ID | Title | Events | Action | Reason |
|---|---|---|---|---|
| PROJ-A | Error in save | 14 | Investigate | User-facing save failure |
| PROJ-B | GM_register... | 3 | Ignore | Greasemonkey extension |
Investigate: multiple events, degraded user experience, high-volume warnings, recurring on every run. Ignore: browser extension code, ChunkLoadError (self-resolving), single-event transients, already fixed.
Apply: mcp__sentry__update_issue(..., status: "ignored") or status: "resolved" for already-fixed.
Phase 2: Investigate (one issue at a time)
Work through these steps in order. Do not skip or batch issues.
1. Pull event-level data — Issue summaries hide details. Use get_issue_details and search_issue_events with naturalLanguageQuery: "all events with extra data". Extract: URLs, params, stack traces, status codes, timestamps.
2. Cross-reference Axiom — Events have traceId. axiom query "['shiori-events'] | where traceId == '<traceId>'" -f json for surrounding context (authMethod, client_version, request metadata).
3. Read the failing code path — Follow the stack trace. Read every file. Understand before proposing changes.
4. Trace the input path upstream (most often skipped, most important) — What data reaches the failing function? Should it have reached this path at all? Is there a missing filter? Is the input wrong (binary URL, redirect, bad format)? Can we prevent bad inputs upstream?
5. Reproduce — Use actual failing inputs from Sentry. Call the function with exact data. fetch() the URLs that timed out. Verify your understanding.
6. Identify root cause — Why does this input fail? Why does it reach this path? What's the right fix? (e.g., "Filter binary URLs before Firecrawl" — not "suppress the log")
| Pattern | Real Fix |
|---|---|
| External API fails on certain URLs | Filter/validate inputs before sending |
| Timeout | Investigate what's slow; adjust timeout or input size |
| DB "invalid json" | Sanitize before insert |
| Stale reference on cron | Detect staleness, auto-clean |
Phase 3: Fix
One branch per issue. git checkout main && git pull && git checkout -b fix/<descriptive-name>
- Tests first — Use data from actual Sentry events. Test fails before fix, passes after.
- Implement — Fix the root cause, not the symptom. If the fix is primarily a log level change, STOP: did you investigate why it fails, or just suppress?
- Verify — Tests pass, lint passes, fix handles actual failing inputs.
- PR — Include Root cause (upstream reason) and Fix (what changed and why it prevents the failure). Resolve in Sentry only after merge.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
What are the valid triage actions?
Only Investigate or Ignore; you decide the fix during investigation, not triage.
Is a log-level downgrade a valid fix?
Only for genuinely expected states, never for failures that have a fallback.
How are issues fixed?
One branch per issue, tests first from actual Sentry event data, fixing the root cause, resolving in Sentry only after merge.