菜单
Use after migrating a route or completing a migration phase to verify correctness. Also use when the build breaks, tests fail, or you suspect migration regressions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding 'use client' directives, splitting mixed components into server + client parts, or fixing RSC boundary errors like "useState only works in a Client Component." Also for migrating interactive UI (forms, modals, event handlers) to App Router.
Use when migrating getStaticProps, getServerSideProps, getStaticPaths, or API routes (pages/api/) to App Router equivalents. Also use when fixing stale data, cache behavior, or fetch errors in migrated pages.
Use when starting a Next.js Pages Router to App Router migration, evaluating migration feasibility, or auditing codebase readiness. Run this BEFORE any other migration skill.
Use when the user asks to plan a Next.js migration, create a migration roadmap, decide migration order, schedule migration phases, or asks "what order should I migrate routes?" Analyzes routes via AST and generates a phased migration plan (.migration/plan.md). Requires migration-assessment first.
Use when converting a specific page from pages/ to app/ directory, or migrating a route end-to-end (file structure, data fetching, metadata, imports). The main workhorse skill for per-route migration.
Use when checking npm package compatibility with App Router, replacing deprecated packages, or auditing dependencies before migration. Covers next/router, next/image legacy, and RSC-incompatible packages.
| name | validation-testing |
| description | Use after migrating a route or completing a migration phase to verify correctness. Also use when the build breaks, tests fail, or you suspect migration regressions. |
Run comprehensive validation checks on migrated code to ensure correctness and catch common migration issues.
NO MIGRATION IS COMPLETE WITHOUT A PASSING BUILD
"It compiles" is not "it works." "The validator passes" is not "the build succeeds." Run every step below. A migration claimed as complete without a passing build is not complete.
This skill requires the nextjs-migration-toolkit skill to be installed. All migration skills depend on it for AST analysis.
TOOLKIT_DIR="$(cd "$(dirname "$SKILL_PATH")/../nextjs-migration-toolkit" && pwd)"
if [ ! -f "$TOOLKIT_DIR/package.json" ]; then
echo "ERROR: nextjs-migration-toolkit is not installed." >&2
echo "Run: npx skills add blazity/next-migration-skills -s nextjs-migration-toolkit" >&2
echo "Then retry this skill." >&2
exit 1
fi
bash "$TOOLKIT_DIR/scripts/setup.sh" >/dev/null
npx tsx "$TOOLKIT_DIR/src/bin/ast-tool.ts" validate <appDir>
This checks for:
next/router imports in app/ files (must use next/navigation)'use client' directives on files using client featuresFor each migrated file:
npx tsx "$TOOLKIT_DIR/src/bin/ast-tool.ts" transform imports <file> --dry-run
Verify all imports use App Router-compatible modules.
For each migrated file:
npx tsx "$TOOLKIT_DIR/src/bin/ast-tool.ts" transform router <file>
Verify no breaking router patterns remain (router.query, router.pathname, router.events, etc.).
Run the Next.js build to catch compilation errors:
npx next build
Common build errors after migration:
npm test
If tests exist, run them to verify behavior is preserved. Common test failures:
'use client' handlingVerify in the browser:
Generate a validation report summarizing:
Save to .migration/validation-report.md.