What problem does it solve? Switching a JavaScript project from Sentry's default transaction-based trace lifecycle to span streaming requires coordinated changes across init options, callbacks, tags, and profiling settings, and missing any one of them causes silent fallback to static mode or lost span data. ## Core Features & Use Cases - Environment Detection: Scans the codebase to classify each Sentry.init call as browser, server, or framework (Next.js, Nuxt, SvelteKit, Remix, Astro) and applies the correct migration path. - Config Migration: Adds traceLifecycle 'stream' on server SDKs or spanStreamingIntegration() on browser SDKs, wraps beforeSendSpan with withStreamedSpan, and updates the callback shape from description/data to name/attributes. - Tag and Transaction Callback Handling: Pairs existing setTag/setTags calls with setAttribute/setAttributes equivalents and migrates beforeSendTransaction logic to beforeSendSpan or ignoreSpans filters. - Use Case: A team running @sentry/nextjs wants spans delivered individually with lower latency; the skill updates both sentry.client.config.ts and sentry.server.config.ts, fixes their beforeSendSpan callback, and verifies the build passes. ## Quick Start Migrate my JavaScript project to Sentry span streaming and update all Sentry.init configurations accordingly.
