next-upgrade

Upgrade Next.js projects across major versions using official migration guides and codemods.

240|75|Updated Dec 3, 2020
One-click install
npx skills add https://github.com/mburumaxwell/paklo --skill next-upgrade-mburumaxwell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-upgrade
Source: https://github.com/mburumaxwell/paklo/tree/main/.agents/skills/next-upgrade
Command: npx skills add https://github.com/mburumaxwell/paklo --skill next-upgrade-mburumaxwell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams upgrade Next.js projects to the latest official version, following migration guides and codemods to minimize manual work and reduce breaking changes.

Core Features & Use Cases

  • Guided upgrades: Detects current Next.js version and suggests an incremental upgrade path (e.g., 13→14→15) with corresponding codemods.
  • Codemod automation: Applies Next.js codemods to automate breaking changes.
  • Dependency updates: Updates next, react, and react-dom in lockstep to compatible versions.
  • Risk mitigation: Reviews breaking changes via official docs and config adjustments (next.config.js) and tests build and dev runs.

Quick Start

Run the upgrade workflow on your project: detect the current Next.js version from package.json, fetch official upgrade documentation and codemods, apply codemods, update dependencies, review changes, and run builds and local tests to verify success.

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 the latest version across multiple major releases?

Upgrading Next.js across major releases requires an incremental path (e.g., 13→14→15) using official migration guides and codemods to update dependencies in lockstep and adjust configurations.

What are Next.js codemods and how do they help with migration?

Next.js codemods are automated scripts that apply breaking code changes during migration, reducing manual work by transforming code patterns to match the target version's requirements.

Can I upgrade Next.js, React, and react-dom dependencies at the same time?

Yes, upgrading Next.js requires updating next, react, and react-dom in lockstep to ensure compatible versions are installed together, preventing runtime errors.

How do I adjust next.config.js when migrating Next.js versions?

Adjusting next.config.js involves reviewing official breaking changes documentation and updating configuration settings to match the target Next.js version's requirements.

What steps should I take if my Next.js build fails after an upgrade?

If a Next.js build fails after an upgrade, review applied codemods and dependency versions, then run build and local test checks to identify and resolve configuration or breaking change issues.

Does this Next.js migration approach work for projects with highly customized configurations?

Yes, this approach works for customized projects by fetching official documentation to review breaking changes, applying codemods, and adjusting next.config.js settings before running build and test checks.