next-upgrade

Upgrades a Next.js project to a newer supported version using codemods and official migration documentation.

Updated May 4, 2026
One-click install
npx skills add https://github.com/jtgiron/portfolio --skill next-upgrade-jtgiron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-upgrade
Source: https://github.com/jtgiron/portfolio/tree/main/.agents/skills/next-upgrade
Command: npx skills add https://github.com/jtgiron/portfolio --skill next-upgrade-jtgiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from moving a Next.js app to a newer major or minor version by guiding the upgrade with official migration steps and codemods.

Core Features & Use Cases

  • Version Detection: Identifies the current Next.js, React, and related dependency versions before planning the upgrade.
  • Official Migration Guidance: Uses the latest Next.js upgrade and codemod documentation to choose the correct path.
  • Incremental Major Upgrades: Handles multi-version jumps by moving through supported upgrade stages in order.
  • Build and Compatibility Checks: Calls out dependency updates, breaking changes, and validation steps needed after the upgrade.
  • Use Case: A team maintaining an older production site can upgrade to a newer Next.js release while minimizing regressions and avoiding undocumented changes.

Quick Start

Ask the assistant to upgrade the current project to the target Next.js version using the official migration guide and codemods.

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 safely?

Upgrading Next.js safely involves detecting current project and React dependency versions, applying official codemods, aligning dependencies, and following migration documentation step by step to minimize breaking changes.

What is the best way to handle a multi-version Next.js migration jump?

A multi-version Next.js migration requires moving through supported incremental upgrade stages in order, applying the correct official codemods and dependency alignment for each stage to prevent regressions.

How do Next.js codemods work during a dependency upgrade?

Next.js codemods automatically transform code based on the latest official upgrade documentation, ensuring compatibility and handling breaking changes while aligning React and related dependencies during the version upgrade.

Can I upgrade a production Next.js application without causing regressions?

Upgrading a production Next.js application safely requires following official migration guidance, executing codemods, and performing build and compatibility checks to call out breaking changes and minimize regressions.

Do I need to update React dependencies when upgrading Next.js?

Updating React dependencies is necessary when upgrading Next.js because the process includes version detection for React and related packages, ensuring dependency compatibility and correct alignment with the target Next.js release.

What are the limitations of using codemods for a Next.js migration?

The limitations of using codemods for a Next.js migration include the need to read project metadata, follow official migration documentation closely, and manually perform build and compatibility checks to catch undocumented changes or edge cases.