Menu
Static help for the guided migration workflow with a final context-aware next-step recommendation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Resume the active guided migration from approval-state scheduler output.
Wizard intake for a new migration. Asks three questions with sensible defaults, then reaches the Component Inventory Review.
Prints a concise status overview of the current migration.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
| name | migrate-help |
| description | Static help for the guided migration workflow with a final context-aware next-step recommendation. |
| disable-model-invocation | true |
You are explaining how to use the Next.js migration plugin. This command is read-only. Do not create .migration/, mutate config, run migration work, or invoke /migrate:continue.
Print this help content in a concise, user-facing format:
Next.js Migration Plugin
Use the guided flow to migrate a public website into a Next.js App Router project with resumable state, component inventory review, component batch approval, and page layout approval.
Commands
- /migrate:new <url> starts a migration and opens Component Inventory Review.
- /migrate:continue resumes the next required approval or implementation step.
- /migrate:status prints current approval, component, page, and queue state.
- /migrate:help shows this help.
Recovery
lower-level scripts and library entry points still exist for maintainers, but they are advanced/recovery tools and are not part of the normal command flow.
Keep the help static even if a local migration exists. Only the final paragraph should depend on local state.
Run the status script and use its JSON to append one final paragraph:
tsx ${PLUGIN_DIR}/lib/status.ts --target "${PWD}"
If ${PLUGIN_DIR} is not set by the harness, resolve it from the plugin install path.
If the script returns initialized: false, append:
No migration in this directory. Start with
/migrate:new <url>.
If the script returns initialized: true, count component and page approval statuses, then append:
Current context: migrating
[sourceUrl]; inventory[approvals.inventory]; components[approved] approved, [pending] pending, [stale] stale; pages[approved] approved, [stale] stale; browser queue concurrency[queueConcurrency]. Next, run/migrate:continueto resume the guided flow, or/migrate:statusfor the full approval summary.
If the status script fails because local state is invalid, append:
Local migration state could not be read:
[error message]. Run/migrate:statusfor the full diagnostic.