What problem does it solve? Upgrading the Sentry JavaScript SDK across major versions (v7 to v8, v8 to v9) involves breaking API changes, removed packages, and renamed methods that cause build failures and runtime errors. This Skill detects your current Sentry setup and walks you through every required code change. ## Core Features & Use Cases - Automated Detection: Scans package.json and source files to identify the current Sentry version, framework (Next.js, Nuxt, SvelteKit, React, Express, NestJS, and more), and deprecated API usage via targeted grep patterns. - Phased Migration Guidance: Categorizes changes into auto-fixable renames, AI-assisted refactors (Hub removal, transaction-to-span migration), and items needing manual review, then applies them file by file. - Version-Specific References: Ships detailed migration references for v7-to-v8, v8-to-v9, and v9-to-v10 covering package removals, API renames, config changes, and behavioral differences. - Use Case: After bumping @sentry/nextjs from v8 to v9 and hitting type errors from getCurrentHub and enableTracing, use this Skill to find every occurrence, apply the replacements, update package versions, and verify the build passes. ## Quick Start Upgrade my Sentry SDK from v8 to v9 and fix all the breaking changes in my project.