next-upgrade

Upgrade Next.js projects across major versions using official codemods.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Happy-Horizon/cursor-marketplace --skill next-upgrade-happy-horizon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-upgrade
Source: https://github.com/Happy-Horizon/cursor-marketplace/tree/main/synced-vendor-skills/.agents/skills/next-upgrade
Command: npx skills add https://github.com/Happy-Horizon/cursor-marketplace --skill next-upgrade-happy-horizon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade Next.js projects safely by following official migration guides and codemods.

Core Features & Use Cases

  • Guided, codemod-driven migration path for major Next.js versions.
  • Dependency synchronization across next, react, and react-dom to minimize conflicts.
  • Validation steps including build and dev server checks to surface breaking changes early.
  • Real-world scenario: upgrading a production project from Next.js 12 to 14 with incremental steps.

Quick Start

Identify your current Next.js version and then follow the codemod-driven upgrade path outlined in this Skill.

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 across major versions safely?

Next.js version detection is required to start the guided codemod-driven migration path, which applies official transforms and synchronizes dependencies to ensure a safe upgrade.

How do codemods help with Next.js migration?

Codemods automate code transformations during a Next.js migration by applying official upgrade paths, ensuring deprecated APIs are updated systematically rather than manually across your project.

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

Yes, upgrading Next.js requires synchronizing dependencies across next, react, and react-dom to minimize conflicts and ensure compatibility with the target version's requirements.

Can I upgrade Next.js from version 12 to 14 in one step?

Upgrading Next.js from 12 to 14 uses incremental version steps, applying codemods sequentially at each major version boundary to catch breaking changes before moving forward.

What is the best way to validate a Next.js upgrade?

The best way to validate a Next.js upgrade is by running build and dev server checks immediately after applying codemods and dependency updates to surface any runtime errors.

Why does my Next.js build break after a major version upgrade?

A Next.js build breaks after an upgrade when dependencies are misaligned or codemods are skipped, making incremental version steps and dependency synchronization essential to resolve conflicts.