/next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods. Use when upgrading Next.js versions, running codemods, or migrating between major releases.
$ npx -y skills add vercel-labs/vercel-plugin --skill next-upgrade --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/next-upgrade
Context preview
The summary Claude sees to decide when to auto-load this skill.
Upgrade Next.js to the latest version following official migration guides and codemods. Use when upgrading Next.js versions, running codemods, or migrating between major releases.
SKILL.md
next-upgrade.SKILL.mdname: next-upgrade
description: Upgrade Next.js to the latest version following official migration guides and codemods. Use when upgrading Next.js versions, running codemods, or migrating between major releases.
metadata:
priority: 6
docs:
- "https://nextjs.org/docs/app/guides/upgrading"
- "https://nextjs.org/docs/app/guides/upgrading/codemods"
pathPatterns:
- 'next.config.*'
- 'package.json'
bashPatterns:
- '\bnpx\s+@next/codemod\b'
- '\bnpm\s+(install|i|add)\s+[^\n]*\bnext@'
- '\bpnpm\s+(install|i|add)\s+[^\n]*\bnext@'
- '\bbun\s+(install|i|add)\s+[^\n]*\bnext@'
- '\byarn\s+add\s+[^\n]*\bnext@'
promptSignals:
phrases:
- "upgrade next"
- "upgrade nextjs"
- "migrate next"
- "update next.js"
- "next.js upgrade"
- "nextjs migration"
- "next codemod"
allOf:
- [upgrade, next]
- [migrate, next]
- [update, nextjs]
anyOf:
- "breaking changes"
- "codemod"
- "migration guide"
- "version upgrade"
noneOf: []
minScore: 6
retrieval:
aliases:
- next upgrade
- nextjs migration
- next codemod
intents:
- upgrade Next.js to latest version
- run Next.js codemods
- migrate between major Next.js versions
entities:
- codemod
- migration
- upgrade
- breaking changes
chainTo:
-
pattern: 'getServerSideProps|getStaticProps|next/router|next/head|next/document'
targetSkill: nextjs
message: 'Pages Router patterns detected during upgrade — loading Next.js best practices for App Router migration.'Upgrade Next.js
Upgrade the current project to the latest Next.js version following official migration guides.
Instructions
1. **Detect current version**: Read `package.json` to identify the current Next.js version and related dependencies (React, React DOM, etc.)
2. **Fetch the latest upgrade guide**: Use WebFetch to get the official upgrade documentation:
- Codemods: https://nextjs.org/docs/app/guides/upgrading/codemods
- Version-specific guides (adjust version as needed):
- https://nextjs.org/docs/app/guides/upgrading/version-16
- https://nextjs.org/docs/app/guides/upgrading/version-15
- https://nextjs.org/docs/app/guides/upgrading/version-14
3. **Determine upgrade path**: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15).
4. **Run codemods first**: Next.js provides codemods to automate breaking changes:
npx @next/codemod@latest <transform> <path>
Common transforms:
- `next-async-request-api` - Updates async Request APIs (v15)
- `next-request-geo-ip` - Migrates geo/ip properties (v15)
- `next-dynamic-access-named-export` - Transforms dynamic imports (v15)
5. **Update dependencies**: Upgrade Next.js and peer dependencies together:
npm install next@latest react@latest react-dom@latest
6. **Review breaking changes**: Check the upgrade guide for manual changes needed:
- API changes (e.g., async params in v15)
- Configuration changes in `next.config.js`
- Deprecated features being removed
7. **Update TypeScript types** (if applicable):
npm install @types/react@latest @types/react-dom@latest
8. **Test the upgrade**:
- Run `npm run build` to check for build errors
- Run `npm run dev` and test key functionality
Read more
name: next-upgrade
description: Upgrade Next.js to the latest version following official migration guides and codemods. Use when upgrading Next.js versions, running codemods, or migrating between major releases.
metadata:
priority: 6
docs:
- "https://nextjs.org/docs/app/guides/upgrading"
- "https://nextjs.org/docs/app/guides/upgrading/codemods"
pathPatterns:
- 'next.config.*'
- 'package.json'
bashPatterns:
- '\bnpx\s+@next/codemod\b'
- '\bnpm\s+(install|i|add)\s+[^\n]*\bnext@'
- '\bpnpm\s+(install|i|add)\s+[^\n]*\bnext@'
- '\bbun\s+(install|i|add)\s+[^\n]*\bnext@'
- '\byarn\s+add\s+[^\n]*\bnext@'
promptSignals:
phrases:
- "upgrade next"
- "upgrade nextjs"
- "migrate next"
- "update next.js"
- "next.js upgrade"
- "nextjs migration"
- "next codemod"
allOf:
- [upgrade, next]
- [migrate, next]
- [update, nextjs]
anyOf:
- "breaking changes"
- "codemod"
- "migration guide"
- "version upgrade"
noneOf: []
minScore: 6
retrieval:
aliases:
- next upgrade
- nextjs migration
- next codemod
intents:
- upgrade Next.js to latest version
- run Next.js codemods
- migrate between major Next.js versions
entities:
- codemod
- migration
- upgrade
- breaking changes
chainTo:
-
pattern: 'getServerSideProps|getStaticProps|next/router|next/head|next/document'
targetSkill: nextjs
message: 'Pages Router patterns detected during upgrade — loading Next.js best practices for App Router migration.'Upgrade Next.js
Upgrade the current project to the latest Next.js version following official migration guides.
Instructions
1. **Detect current version**: Read `package.json` to identify the current Next.js version and related dependencies (React, React DOM, etc.)
2. **Fetch the latest upgrade guide**: Use WebFetch to get the official upgrade documentation:
- Codemods: https://nextjs.org/docs/app/guides/upgrading/codemods
- Version-specific guides (adjust version as needed):
- https://nextjs.org/docs/app/guides/upgrading/version-16
- https://nextjs.org/docs/app/guides/upgrading/version-15
- https://nextjs.org/docs/app/guides/upgrading/version-14
3. **Determine upgrade path**: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15).
4. **Run codemods first**: Next.js provides codemods to automate breaking changes:
npx @next/codemod@latest <transform> <path>
Common transforms:
- `next-async-request-api` - Updates async Request APIs (v15)
- `next-request-geo-ip` - Migrates geo/ip properties (v15)
- `next-dynamic-access-named-export` - Transforms dynamic imports (v15)
5. **Update dependencies**: Upgrade Next.js and peer dependencies together:
npm install next@latest react@latest react-dom@latest
6. **Review breaking changes**: Check the upgrade guide for manual changes needed:
- API changes (e.g., async params in v15)
- Configuration changes in `next.config.js`
- Deprecated features being removed
7. **Update TypeScript types** (if applicable):
npm install @types/react@latest @types/react-dom@latest
8. **Test the upgrade**:
- Run `npm run build` to check for build errors
- Run `npm run dev` and test key functionality
Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel expert.
Repo: vercel-labs/vercel-plugin
Other skills on vercel.
- /benchmark-agents
Advanced AI agent benchmark scenarios that push Vercel's cutting-edge platform features — Workflow DevKit, AI Gateway, MCP, Chat SDK, Queues, Flags, Sandbox, and multi-agent orchestration. Designed to stress-test skill injection for complex, multi-system builds.
Open skill - /benchmark-e2e
End-to-end benchmark suite for vercel-plugin. Runs realistic projects through skill injection, launches dev servers, verifies everything works, analyzes conversation logs, and produces an improvement report for overnight self-improvement loops.
Open skill - /benchmark-sandbox
Run vercel-plugin eval scenarios in Vercel Sandboxes instead of local WezTerm panels. Provisions ephemeral microVMs with Claude Code + plugin pre-installed, runs benchmark prompts, extracts hook artifacts, and produces coverage reports.
Open skill - /benchmark-testing
Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios. Sets up isolated directories, installs the plugin, and spawns WezTerm panes running Claude Code with crafted prompts.
Open skill - /plugin-audit
Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache staleness. Use when asked to audit, test, or investigate plugin
Open skill - /release
Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".
Open skill

