next-upgrade

Automate incremental Next.js upgrades with codemods and dependency updates.

1|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Asymmetric-al/asym-web --skill next-upgrade-asymmetric-al
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-upgrade
Source: https://github.com/Asymmetric-al/asym-web/tree/main/.agents/skills/next-upgrade
Command: npx skills add https://github.com/Asymmetric-al/asym-web --skill next-upgrade-asymmetric-al

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading Next.js to newer major or minor releases can introduce breaking changes, compatibility issues with React/TypeScript, and potential upgrade-path gaps. This skill provides a structured, codemod-driven workflow to move projects forward while preserving functionality and stability.

Core Features & Use Cases

  • Incremental upgrade planning: detects current Next.js version, React/React DOM versions, and maps an upgrade path (e.g., 13 → 14 → 15 → 16).
  • Codemod automation: applies official Next.js codemods to automate breaking changes and reduce manual edits.
  • Dependency alignment & validation: updates next, react, and react-dom to latest compatible versions and verifies TypeScript typings if present.
  • Build and test validation: runs build and dev checks to validate the upgrade impact and catch issues early.

Quick Start

Upgrade Next.js to the latest version by following the official guides and applying codemods automatically.

Frequently Asked Questions about next-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Next.js to a newer major version without breaking changes?

To upgrade Next.js safely, apply official codemods that automate breaking changes and update dependencies like react and react-dom to compatible versions. This structured approach preserves functionality while moving projects forward incrementally.

What is the best way to automate a Next.js migration across multiple versions?

Automating a Next.js migration involves detecting your current version via package.json, mapping an incremental upgrade path, and applying official codemods to reduce manual edits. This ensures dependency alignment and validates build stability across versions.

Can I upgrade Next.js and React together in a TypeScript project?

Yes, you can upgrade Next.js and React together in a TypeScript project. The process updates next, react, and react-dom to latest compatible versions and verifies TypeScript typings to ensure type safety and dependency alignment.

Does the Next.js upgrade process validate builds and catch compatibility issues early?

Yes, the Next.js upgrade process runs build and dev checks to validate the upgrade impact and catch issues early. This validation step ensures that breaking changes from codemods and dependency updates do not disrupt functionality.

How do codemods work when updating Next.js dependencies?

Codemods automate breaking changes by transforming your codebase to match new Next.js APIs. They reduce manual edits during the dependency update process, ensuring your react and react-dom versions align with the latest Next.js release.

What should I do if my Next.js build fails after a major version upgrade?

If your Next.js build fails after an upgrade, verify dependency alignment for react, react-dom, and TypeScript typings. Running build and dev validation checks helps catch compatibility issues and identify missing codemod transformations early.