How do I install the Nextjs Upgrade skill?

Run npx skillmds@latest add filippodesilva/nextjs-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 Nextjs Upgrade safe to use?

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

Which AI agents work with Nextjs 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 Nextjs Upgrade free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Nextjs Upgrade?

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

Nextjs Upgrade by filippodesilva — Agent Skill

Name: Nextjs Upgrade
Author: FilippoDeSilva

File contents

Next.js Upgrade Protocol

Automated and manual migration steps for Next.js version upgrades (e.g., v14 to v15).

Priority: P1 (OPERATIONAL)

Workflow: Upgrade Next.js to New Major Version

Check current versions of next, react, react-dom in package.json
Plan incremental path (e.g., v13 -> v14 -> v15; never skip majors)
Run codemods: npx @next/codemod@latest <transform> <path>
Update dependencies: See implementation examples
Verify async APIs: ensure cookies(), headers(), params awaited (v15+)
Audit fetch caching: v15 defaults to no-store; add force-cache where needed
Run next build and fix hydration or Turbopack errors
Report codemod failures or manual fixes to team

Implementation Guidelines

Upgrade Detection: Always check package.json for versions of next, react, and react-dom.
Planning: For major version jumps (v13 to v15), perform incremental upgrade (v13 -> v14, then v14 -> v15). Follow official Next.js Migration Guides.
Automated Codemods: Use npx @next/codemod@latest <transform> <path> to automate syntax migration.
Breaking Changes (v15): Respond to next-async-request-api transform by ensuring params, searchParams, cookies(), and headers() awaited.
React Parity: Upgrade react and react-dom to match Next.js peer dependencies (e.g., React 19 for Next.js 15).
Validation: Run next dev and next build after each incremental step. Check console errors for hydration warnings.

Anti-Patterns

No major version skipping: Upgrade one major version at time (13 -> 14, then 14 -> 15).
No manual breaking-change fixes: Always run npx @next/codemod@latest transforms first.
No assumed caching behavior post-upgrade: v15 defaults to no-store; audit all fetch calls.
No async page functions in Pages Router: export default async function Page() fatal.

---name: nextjs-upgradedescription: Next.js version migrations using official guides and codemods. Use when migrating a Next.js project to a new major version using codemods.license: MIT---# Next.js Upgrade ProtocolAutomated and manual migration steps for Next.js version upgrades (e.g., v14 to v15).## **Priority: P1 (OPERATIONAL)**## Workflow: Upgrade Next.js to New Major Version1. Check current versions of `next`, `react`, `react-dom` in `package.json`2. Plan incremental path (e.g., v13 -> v14 -> v15; never skip majors)3. Run codemods: `npx @next/codemod@latest <transform> <path>`4. Update dependencies: See [implementation examples](references/example.md)5. Verify async APIs: ensure `cookies()`, `headers()`, `params` awaited (v15+)6. Audit `fetch` caching: v15 defaults to `no-store`; add `force-cache` where needed7. Run `next build` and fix hydration or Turbopack errors8. Report codemod failures or manual fixes to team## Implementation Guidelines- **Upgrade Detection**: Always check `package.json` for versions of `next`, `react`, and `react-dom`.- **Planning**: For major version jumps (v13 to v15), perform incremental upgrade (v13 -> v14, then v14 -> v15). Follow official Next.js Migration Guides.- **Automated Codemods**: Use `npx @next/codemod@latest <transform> <path>` to automate syntax migration.- **Breaking Changes (v15)**: Respond to `next-async-request-api` transform by ensuring `params`, `searchParams`, `cookies()`, and `headers()` awaited.- **React Parity**: Upgrade `react` and `react-dom` to match Next.js peer dependencies (e.g., React 19 for Next.js 15).- **Validation**: Run `next dev` and `next build` after each incremental step. Check console errors for hydration warnings.## Anti-Patterns- **No major version skipping**: Upgrade one major version at time (13 -> 14, then 14 -> 15).- **No manual breaking-change fixes**: Always run `npx @next/codemod@latest` transforms first.- **No assumed caching behavior post-upgrade**: v15 defaults to `no-store`; audit all `fetch` calls.- **No async page functions in Pages Router**: `export default async function Page()` fatal.

Frequently asked questions

Nextjs Upgrade