How do I install the Next Upgrade skill?

Run npx skillmds@latest add georgekhananaev/next-upgrade in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Next Upgrade safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Next Upgrade?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Next Upgrade free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Next Upgrade?

georgekhananaev (@georgekhananaev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Next Upgrade by georgekhananaev — Agent Skill

Name: Next Upgrade
Rating: 4.666666666666667 (3 reviews)
Author: georgekhananaev

File contents

Upgrade Next.js

Upgrade the current project to the latest Next.js version following official migration guides.

Instructions

Detect current version: Read package.json to identify the current Next.js version and related dependencies (React, React DOM, etc.)
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
Determine upgrade path: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15 → 16).
Prefer the automated path first: the official upgrade codemod bumps deps AND runs the right transforms interactively:
```
npx @next/codemod@latest upgrade latest   # or: upgrade patch|minor|major|<version>
next upgrade                              # built-in self-upgrade command (Next 16.1+)
```
Fall back to individual codemods when the automated path can't run:
```
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)
- remove-experimental-ppr / remove-unstable-prefix - PPR & unstable_* cleanup (v16)
- middleware-to-proxy - middleware.ts → proxy.ts (v16)
- next-lint-to-eslint-cli - migrate off next lint (v16)
Update dependencies: Upgrade Next.js and peer dependencies together:
```
npm install next@latest react@latest react-dom@latest
```
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

Update TypeScript types (if applicable):

npm install @types/react@latest @types/react-dom@latest

Test the upgrade:
- ASK the user before running npm run build (builds are slow; some users forbid unprompted builds)
- Run npm run dev and test key functionality

---name: next-upgradedescription: Upgrade Next.js to the latest version following official migration guides and codemods---# Upgrade Next.jsUpgrade the current project to the latest Next.js version following official migration guides.## Instructions1. **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-153. **Determine upgrade path**: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15 → 16).4. **Prefer the automated path first**: the official upgrade codemod bumps deps AND runs the right transforms interactively: ```bash npx @next/codemod@latest upgrade latest # or: upgrade patch|minor|major|<version> next upgrade # built-in self-upgrade command (Next 16.1+) ``` Fall back to individual codemods when the automated path can't run: ```bash 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) - `remove-experimental-ppr` / `remove-unstable-prefix` - PPR & unstable_* cleanup (v16) - `middleware-to-proxy` - middleware.ts → proxy.ts (v16) - `next-lint-to-eslint-cli` - migrate off `next lint` (v16)5. **Update dependencies**: Upgrade Next.js and peer dependencies together: ```bash 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 removed7. **Update TypeScript types** (if applicable): ```bash npm install @types/react@latest @types/react-dom@latest ```8. **Test the upgrade**: - ASK the user before running `npm run build` (builds are slow; some users forbid unprompted builds) - Run `npm run dev` and test key functionality

Frequently asked questions

Next Upgrade