next-upgrade

スター0

フォーク0

更新日2026年3月23日 15:34

Upgrade Next.js to the latest version following official migration guides and codemods

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

wcpos

wcpos/wcpos-com

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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):
Determine upgrade path: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15 → 16).
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)
Update dependencies: Upgrade Next.js and peer dependencies using the repo's package manager (detect via lockfile: pnpm-lock.yaml → pnpm, yarn.lock → yarn, package-lock.json → npm):
```
pnpm add 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):

pnpm add -D @types/react@latest @types/react-dom@latest

Test the upgrade:
- Run pnpm build to check for build errors
- Run pnpm dev and test key functionality

このリポジトリの他の Skills

同じリポジトリ

next-best-practices

wcpos/wcpos-com

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

2026-03-230

storefront-best-practices

wcpos/wcpos-com

ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React, Vue). Provides patterns, decision frameworks, backend integration guidance.

2026-03-230

next-cache-components

wcpos/wcpos-com

Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

2026-03-230

name	next-upgrade
user-invocable	true
description	Upgrade Next.js to the latest version following official migration guides and codemods
allowed-tools	["Bash","Read","Write","Edit","Glob","Grep","WebFetch"]

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):
Determine upgrade path: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15 → 16).
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)
Update dependencies: Upgrade Next.js and peer dependencies using the repo's package manager (detect via lockfile: pnpm-lock.yaml → pnpm, yarn.lock → yarn, package-lock.json → npm):
```
pnpm add 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):

pnpm add -D @types/react@latest @types/react-dom@latest

Test the upgrade:
- Run pnpm build to check for build errors
- Run pnpm dev and test key functionality