Summary
This is a workflow for actually fixing Sentry errors instead of just closing them. It walks Claude through three phases: triage (using Sentry MCP to find and classify issues), investigation (pulling event details, cross-referencing with Axiom logs by traceId, tracing upstream inputs), and fixing with tests. The philosophy is pretty clear: treat errors as signals pointing to root causes, not noise to suppress. It explicitly bans common shortcuts like batch-ignoring issues, downgrading log levels without investigation, or treating fallbacks as acceptable. You'd use this when production errors pile up and you need systematic debugging rather than whack-a-mole fixes. Requires the Sentry MCP server already configured.
Install to Claude Code
npx -y skills add brianlovin/claude-config --skill fix-sentry-issues --agent claude-codeInstalls into .claude/skills of the current project.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.md
Select a file.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
