Official agent skill

Sentry SDK Upgrade

Upgrade the Sentry JavaScript SDK across major versions. An agent skill from getsentry/sentry-for-ai.

OfficialApache-2.0Auto-check passedDevelopment

Install Sentry SDK Upgrade

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .claude/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .claude/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .agents/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .agents/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .cursor/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .cursor/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/getsentry/sentry-for-ai.git --path skills-legacy/sentry-sdk-upgrade

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .gemini/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .gemini/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .github/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .github/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install getsentry/sentry-for-ai sentry-sdk-upgrade --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills-legacy/sentry-sdk-upgrade .opencode/skills/sentry-sdk-upgrade && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sentry-sdk-upgrade" agent skill from https://github.com/getsentry/sentry-for-ai/tree/main/skills-legacy/sentry-sdk-upgrade into .opencode/skills/sentry-sdk-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-sdk-upgrade", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sentry-sdk-upgrade
GitHub stars: 268
Token cost: ~2.1k tokens
SKILL.md length: 779 words
Files: 5 (incl. references)
Skills in repo: 32
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Upgrade the Sentry JavaScript SDK across major versions. An agent skill from getsentry/sentry-for-ai.

Works in 4 steps: Detect → Recommend → Guide → …
Asked to upgrade Sentry
SKILL.md covers Invoke This Skill When, Phase 1: Detect, Phase 2: Recommend and Phase 3: Guide, plus 1 more section
Calls npx and npm

What it does

Sentry SDK Upgrade is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization. Upgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/upgrade-patterns.md`, `references/v7-to-v8.md` and `references/v8-to-v9.md`).

It sits in Development. It works with Sentry, JavaScript, npm and Nuxt. The repository describes itself as: Teach your AI coding assistant how to use Sentry - setup, debugging, alerts, and more. The licence is Apache-2.0.

When your agent uses it

Asked to upgrade Sentry
Migrate to a newer version
Fix deprecated Sentry APIs
Resolve breaking changes after a Sentry version bump

Example prompts

“/sentry-sdk-upgrade”

Requirements

Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Detect
Recommend
Guide
Cross-Link

What it can do on your machine

Read from SKILL.md and the folder at commit d8fd106. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- docs.sentry.io
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sentry SDK Upgrade loads about 2.1k tokens when it runs, and up to ~8.7k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 779 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~56
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~8.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getsentry/sentry-for-ai at commit d8fd106, republished under its Apache-2.0 licence (© getsentry). 779 words, ~2,141 tokens.

Download SKILL.mdSave it as .claude/skills/sentry-sdk-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: sentry-sdk-upgrade
description: Upgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump.
license: Apache-2.0
category: workflow
parent: sentry-workflow
disable-model-invocation: true

All Skills > Workflow > SDK Upgrade

Sentry JavaScript SDK Upgrade

Upgrade the Sentry JavaScript SDK across major versions with AI-guided migration.

Invoke This Skill When

User asks to "upgrade Sentry" or "migrate Sentry SDK"
User mentions deprecated Sentry APIs or breaking changes after a version bump
User wants to move from v7 to v8, v8 to v9, or any major version jump
User encounters errors after updating @sentry/* package versions
User asks about Sentry migration guides or changelogs

Phase 1: Detect

Identify the current Sentry SDK version, target version, and framework.

1.1 Read package.json

bash

cat package.json | grep -E '"@sentry/' | head -20

Extract:

All @sentry/* packages and their current versions
The current major version (e.g., 7.x, 8.x, 9.x)

1.2 Detect Framework

Check package.json dependencies for framework indicators:

Dependency	Framework	Sentry Package
`next`	Next.js	`@sentry/nextjs`
`nuxt` or `@nuxt/kit`	Nuxt	`@sentry/nuxt`
`@sveltejs/kit`	SvelteKit	`@sentry/sveltekit`
`@remix-run/node`	Remix	`@sentry/remix`
`react` (no Next/Remix)	React SPA	`@sentry/react`
`@angular/core`	Angular	`@sentry/angular`
`vue` (no Nuxt)	Vue	`@sentry/vue`
`express`	Express	`@sentry/node`
`@nestjs/core`	NestJS	`@sentry/nestjs`
`@solidjs/start`	SolidStart	`@sentry/solidstart`
`astro`	Astro	`@sentry/astro`
`bun` types or runtime	Bun	`@sentry/bun`
`@cloudflare/workers-types`	Cloudflare	`@sentry/cloudflare`
None of above (Node.js)	Node.js	`@sentry/node`

1.3 Find Sentry Config Files

bash

grep -rn "from '@sentry/\|require('@sentry/" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" --include="*.mjs" --include="*.cjs" -l

bash

find . -name "sentry.*" -o -name "*.sentry.*" -o -name "instrumentation.*" | grep -v node_modules | grep -v .next | grep -v .nuxt

1.4 Detect Deprecated Patterns

Scan for patterns that indicate which migration steps are needed:

bash

# v7 patterns (need v7→v8 migration)
grep -rn "from '@sentry/hub'\|from '@sentry/tracing'\|from '@sentry/integrations'\|from '@sentry/serverless'\|from '@sentry/replay'" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" -l
grep -rn "new BrowserTracing\|new Replay\|startTransaction\|configureScope\|Handlers\.requestHandler\|Handlers\.errorHandler" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" -l

# v8 patterns (need v8→v9 migration)
grep -rn "from '@sentry/utils'\|from '@sentry/types'" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" -l
grep -rn "getCurrentHub\|enableTracing\|captureUserFeedback\|@WithSentry\|autoSessionTracking" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" -l

1.5 Determine Target Version

If the user didn't specify a target version, recommend the latest major version (v9 as of this writing). If the user has already bumped package versions but has broken code, detect the target from package.json.

Present a migration summary based on detected state.

2.1 Calculate Migration Path

Single hop: e.g., v8 to v9
Multi-hop: e.g., v7 to v9 (apply v7→v8 changes first, then v8→v9)

For multi-hop migrations, apply code changes incrementally but update package versions once to the final target.

2.2 Present Breaking Changes Summary

Load the appropriate version-specific reference:

Present a concrete summary of changes needed, categorized by complexity:

Auto-fixable (apply directly):

Package import renames (e.g., @sentry/utils to @sentry/core)
Simple method renames (e.g., @WithSentry to @SentryExceptionCaptured)
Config option swaps (e.g., enableTracing to tracesSampleRate)

AI-assisted (explain and propose):

Hub removal with variable storage patterns
Performance API migration (transactions to spans)
Complex config restructuring (Vue tracing options, Next.js config merging)
Sampler transactionContext flattening

Manual review (flag for user):

Removed APIs with no equivalent
Behavioral changes (sampling, source maps defaults)
Custom transport modifications

2.3 Confirm Scope

Ask the user:

Confirm the migration path (e.g., "v8 to v9")
Confirm whether to proceed with all changes or specific categories
Note: npx @sentry/wizard -i upgrade exists as a CLI alternative for v8→v9 but may not handle all patterns

Phase 3: Guide

Step through changes file by file.

3.1 Process Each File with Sentry Imports

For each file identified in Phase 1.3:

Read the file to understand current Sentry usage
Apply auto-fixable changes directly:
- Package import renames
- Method/function renames
- Simple config option swaps
For AI-assisted changes, explain what needs to change and why, then propose the specific edit
For uncertain changes, show the code and ask the user to confirm

Show full SKILL.md (282 more words)Show less

3.2 Apply Changes by Category

Work through changes in this order:

Step 1: Package Import Updates

Replace removed/renamed package imports. Reference the version-specific migration file for the complete mapping.

Step 2: API Renames

Apply mechanical method and function renames.

Step 3: Config Changes

Update Sentry.init() options and build configuration.

Step 4: Complex Pattern Migration

Handle patterns requiring understanding of context:

Hub usage stored in variables
Transaction-based performance code
Custom integration classes
Framework-specific wrappers

Step 5: Update package.json Versions

Update all @sentry/* packages to the target version. All packages must be on the same major version.

bash

# Detect package manager
if [ -f "yarn.lock" ]; then
  echo "yarn"
elif [ -f "pnpm-lock.yaml" ]; then
  echo "pnpm"
else
  echo "npm"
fi

Install updated dependencies using the detected package manager.

Step 6: Verify Build

bash

# Check for type errors
npx tsc --noEmit 2>&1 | head -50

# Run build
npm run build 2>&1 | tail -20

Fix any remaining type errors or build failures.

3.3 Framework-Specific Steps

Consult references/upgrade-patterns.md for framework-specific config file locations and validation steps.

Next.js: Check instrumentation.ts, next.config.ts wrapper, both client and server configs. Nuxt: Check Nuxt module config and both plugin files. SvelteKit: Check hooks files and Vite config. Express/Node: Verify early initialization order. NestJS: Check for decorator and filter renames.

Phase 4: Cross-Link

4.1 Verify

All @sentry/* packages on same version
No import errors from removed packages
TypeScript compilation passes
Build succeeds
Tests pass (if they exist)

Suggest adding a test error:

// Add temporarily to verify Sentry is working after upgrade
setTimeout(() => {
  throw new Error('Sentry upgrade verification - safe to delete');
}, 3000);

4.2 New Features in Target Version

Mention features available in the new version that the user might want to enable:

v8 new features: OpenTelemetry-based Node tracing, automatic database/HTTP instrumentation, functional integrations, new span APIs

v9 new features: Structured logging (Sentry.logger.*), improved source maps handling, simplified configuration

If the user has other Sentry SDKs (Python, Ruby, Go, etc.) that also need upgrading, note that this skill covers JavaScript SDK only.

Files

SKILL.md and 4 other files (references) in skills-legacy/sentry-sdk-upgrade of getsentry/sentry-for-ai.

SKILL.md
references/upgrade-patterns.md
references/v7-to-v8.md
references/v8-to-v9.md
references/v9-to-v10.md

Open the folder on GitHubat commit d8fd106

Compare with similar skills

Sentry SDK Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sentry SDK Upgrade compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sentry SDK Upgrade this skillgetsentry/sentry-for-ai	268	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Sanity Best Practicesrobotostudio/turbo-start-sanity	182	—	~940	Automated safety check: Pass	MIT	2 days ago
Launch With AWSaws/agent-toolkit-for-aws	2.8k	—	~3.2k	Automated safety check: Pass	Apache-2.0	today
Sanity Best Practicessanity-io/agent-toolkit	188	—	~1.3k	Automated safety check: Pass	MIT	2 days ago
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop	5.3k	1 repos	~2.2k	Automated safety check: Pass	MIT	27 days ago
Version ReleaseNG-ZORRO/ng-zorro-antd	9.2k	—	~3.1k	Automated safety check: Pass	MIT	today

Similar skills

Sanity Best Practices
robotostudio/turbo-start-sanity
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and…
182 GitHub stars~940 tokensUpdated 2 days ago
Frontend & DesignAuto-check passed
Launch With AWS
aws/agent-toolkit-for-aws
Official
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
2.8k GitHub stars~3.2k tokensUpdated today
Frontend & DesignAuto-check passed
Sanity Best Practices
sanity-io/agent-toolkit
Official
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints…
188 GitHub stars~1.3k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
5.3k GitHub starsUsed in 1 repo~2.2k tokens
DevelopmentAuto-check passed
Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
9.2k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
2.8k GitHub stars~2k tokensUpdated 19 days ago
DevelopmentAuto-check passed

Questions about Sentry SDK Upgrade

What does Sentry SDK Upgrade do?

Upgrade the Sentry JavaScript SDK across major versions. An agent skill from getsentry/sentry-for-ai. Sentry SDK Upgrade is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization. Upgrade the Sentry JavaScript SDK across major versions.

When should I use Sentry SDK Upgrade?

Sentry SDK Upgrade fits situations like: asked to upgrade Sentry; migrate to a newer version; fix deprecated Sentry APIs; resolve breaking changes after a Sentry version bump.

How do I install Sentry SDK Upgrade in Claude Code?

Run `npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a claude-code`. Or copy the skill folder (skills-legacy/sentry-sdk-upgrade in getsentry/sentry-for-ai) into .claude/skills/sentry-sdk-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Sentry SDK Upgrade in Codex?

Run `npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a codex`. Or copy the skill folder (skills-legacy/sentry-sdk-upgrade in getsentry/sentry-for-ai) into .agents/skills/sentry-sdk-upgrade in your project. Codex loads it when a task matches its description.

Can I use Sentry SDK Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry-for-ai --skill sentry-sdk-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-sdk-upgrade, .gemini/skills/sentry-sdk-upgrade, .github/skills/sentry-sdk-upgrade and .opencode/skills/sentry-sdk-upgrade in your project.

What does Sentry SDK Upgrade need to run?

Going by SKILL.md and its folder, Sentry SDK Upgrade needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.

Does Sentry SDK Upgrade access the network?

SKILL.md names 2 domains. As links in the text: docs.sentry.io and github.com. This is read from the text; nothing was executed.

Is Sentry SDK Upgrade safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sentry SDK Upgrade use?

Sentry SDK Upgrade is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sentry SDK Upgrade use?

About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.6k tokens, read only when the agent opens those files.

What are the alternatives to Sentry SDK Upgrade?

Skills that share tags, products or a category with Sentry SDK Upgrade: Sanity Best Practices (robotostudio/turbo-start-sanity, 182 stars), Launch With AWS (aws/agent-toolkit-for-aws, 2.8k stars), Sanity Best Practices (sanity-io/agent-toolkit, 188 stars) and Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry SDK Upgrade?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry-for-ai, which has 268 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.

Source: getsentry/sentry-for-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sentry SDK Upgrade

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Sentry JavaScript SDK Upgrade

Invoke This Skill When

Phase 1: Detect

1.1 Read package.json

1.2 Detect Framework

1.3 Find Sentry Config Files

1.4 Detect Deprecated Patterns

1.5 Determine Target Version

Phase 2: Recommend

2.1 Calculate Migration Path

2.2 Present Breaking Changes Summary

2.3 Confirm Scope

Phase 3: Guide

3.1 Process Each File with Sentry Imports

3.2 Apply Changes by Category

Step 1: Package Import Updates

Step 2: API Renames

Step 3: Config Changes

Step 4: Complex Pattern Migration

Step 5: Update package.json Versions

Step 6: Verify Build

3.3 Framework-Specific Steps

Phase 4: Cross-Link

4.1 Verify

4.2 New Features in Target Version

4.3 Related Resources

Files

Compare with similar skills

Similar skills

More from getsentry/sentry-for-ai

Related

Questions about Sentry SDK Upgrade