What problem does it solve? Debugging production errors from Sentry reports is time-consuming: you must manually correlate stack traces, breadcrumbs, traces, and replays before you can even form a root-cause hypothesis. This Skill provides a methodical seven-phase workflow that uses the Sentry MCP server to gather full issue context, identify root causes, implement fixes, and verify them. ## Core Features & Use Cases - Issue Discovery & Triage: Search unresolved Sentry issues by error type, date, or issue ID using Sentry MCP tools, then confirm targets before fixing. - Deep Context Analysis: Pull stack traces, breadcrumbs, tags, distributed traces, and session replays to build an evidence-backed root cause hypothesis. - Guided Fix & Verification: Apply fixes following codebase patterns, add regression tests reproducing exact Sentry event conditions, and complete a verification audit before reporting. - Use Case: A TypeError spike appears in your Next.js app after a deploy. Ask the assistant to investigate the Sentry issue; it retrieves the stack trace and breadcrumbs, traces the data flow to an unvalidated API response, implements input validation, and adds a regression test. ## Quick Start Ask the assistant to find the most recent unresolved Sentry issues and fix the top one, confirming the issue with you before making code changes.