Upgrade Next.js to the latest version following official migration guides and codemods
68
53%
Does it follow best practices?
Impact
93%
1.25xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/next-upgrade/SKILL.mdIncremental upgrade path and codemod usage
Reads package.json
100%
100%
Incremental path
100%
100%
Codemods before deps
100%
100%
Uses @next/codemod
100%
100%
next-async-request-api codemod
100%
100%
next-dynamic-access-named-export codemod
0%
0%
Dependencies installed together
100%
100%
Fetches official upgrade docs
100%
100%
Breaking changes mentioned
100%
100%
Test commands included
100%
100%
TypeScript types update and dependency install order
Reads package.json
100%
100%
Codemods before install
0%
66%
next-async-request-api applied
50%
100%
Core deps together
100%
100%
TypeScript types updated
100%
100%
Types installed separately
100%
100%
Official docs consulted
100%
100%
API breaking changes
100%
100%
next.config.js review
100%
100%
Build verification step
100%
100%
Breaking changes review and official docs fetching
Reads package.json
100%
83%
Fetches nextjs.org docs
0%
100%
next-request-geo-ip codemod
0%
100%
next-dynamic-access-named-export codemod
0%
100%
Uses @next/codemod CLI
100%
100%
Async params breaking change
100%
100%
next.config.js changes
0%
0%
Codemods before install
80%
100%
Dependencies together
30%
100%
Verification step
100%
100%
dc1de9c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.