fix-sentry-issues
Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".
- Installs
- 2.7K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/brianlovin/agent-config --skill fix-sentry-issues- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads fix-sentry-issues automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
-
Pull event-level data — Issue summaries hide details. Use
get_issue_detailsandsearch_issue_eventswithnaturalLanguageQuery: "all events with extra data". Extract: URLs, params, stack traces, status codes, timestamps. -
Cross-reference Axiom — Events have
traceId.axiom query "['shiori-events'] | where traceId == '<traceId>'" -f jsonfor surrounding context (authMethod, client_version, request metadata). -
Read the failing code path — Follow the stack trace. Read every file. Understand before proposing changes.
-
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?
-
Reproduce — Use actual failing inputs from Sentry. Call the function with exact data.
fetch()the URLs that timed out. Verify your understanding. -
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.
FAQ
What does the fix-sentry-issues skill do?
Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".
How do I install fix-sentry-issues?
Run npx skills add https://github.com/brianlovin/agent-config --skill fix-sentry-issues in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/fix-sentry-issues/ (personal) or .claude/skills/fix-sentry-issues/ (project).
Which AI agents can use fix-sentry-issues?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is fix-sentry-issues safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains fix-sentry-issues?
It is published by brianlovin in brianlovin/agent-config. It has 2,747 recorded installs.
More from brianlovin/agent-config
simplify
brianlovin/agent-config
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
deslop
brianlovin/agent-config
Remove AI-generated code slop from the current branch. Use after writing code to clean up unnecessary comments, defensive checks, and inconsistent style.
knip
brianlovin/agent-config
Run knip to find and remove unused files, dependencies, and exports. Use for cleaning up dead code and unused dependencies.
rams
brianlovin/agent-config
Run accessibility and visual design review on components. Use when reviewing UI code for WCAG compliance and design issues.
find-skills
brianlovin/agent-config
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
agent-browser
brianlovin/agent-config
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.