Agent skill · software engineering · jeremylongshore
sentry-upgrade-migration
Upgrade Sentry SDK versions and migrate breaking API changes.
Why this skill is useful
Adds an automated migration script for upgrading Sentry SDK versions that includes codemods and validation steps not found in public documentation.
What it needs
Requires npm, pip installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Upgrade Migration Detect installed Sentry SDK versions, identify breaking API changes, apply automated codemods, and verify the upgrade succeeds with test events and traces. Current State !npm list 2>/dev/null command grep @sentry echo 'No npm Sentry packages found' !pip show sentry-sdk 2>/dev/null command grep -E '^(Name Version)' echo 'No Python sentry-sdk found' !node --version 2>/dev/null echo 'Node.js not available' Overview Sentry SDK upgrades require careful handling of breaking API changes. The v7 to v8 JavaScript migration is the most impactful, removing the Hub pattern, replacing Transaction/Span APIs with startSpan(), converting class-based integrations to functions, and requiring ESM-first initialization. Python SDK v1 to v2 similarly replaces configurescope() with getcurrentscope(). This skill automates version detection, runs the official @sentry/migr8 codemod, applies manual fixes for patterns the codemod misses, and validates the upgrade with test events. Prerequisites Current Sentry SDK version identified (run DCI above) Target version changelog reviewed Non-production environment for testing upgrades All @sentry/ packages at the same major version before starting Node.js >= 18.19.0 or >= 20.6.0 for SDK v8 (ESM support required) Instructions Step 1. Identify Current SDK Version and Scan for Deprecated APIs Scan the codebase for deprecated patterns that need migration: Step 2. Run the Automated Migration Codemod (JavaScript v7 to v8) Step 3. Apply Breaking Change Fixes the Codemod Misses Breaking Change: Transaction/Span API replaced with startSpan() Breaking Change: Hub removed, use Scope API Breaking Change: Integrations are functions, not classes Breaking Change: @sentry/tracing removed Breaking Change: ESM initialization requires separate file Breaking Change: Custom transport must return response See major-version-migrations.md for v6-to-v7 and Python v1-to-v2 migration details. Step 4. Python SDK v1 to v2 Migration Step 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-upgrade-migration--a62654