nuxt4-migration
Skill2 starsChanged 55 days agoNo licenceView on GitHub
Audits a Nuxt 3 project for Nuxt 4 migration readiness and drives the migration — runs `nuxt upgrade` and the official codemods, checks each breaking-change area (directory structure, useAsyncData/useFetch behaviour, normalized component names, inline styles, Unhead v2, TypeScript config, window.__NUXT__, removed config), audits and bumps the module ecosystem (Node version, Nuxt modules, TypeScript/Vite) to Nuxt-4-compatible versions, and produces a prioritized migration plan. Use when the user asks to migrate/upgrade a Nuxt project to v4, or invokes /gm:nuxt4-migration.
In this repository19 other files it gives its agents.
- angularSkill
- archi-c4Skill
- checklist-quality-auditSkill
- cqaSkill
- djangoSkill
- docker-devopsSkill
- drupalSkill
- laravelSkill
- merge-requestSkill
- merge-reviewSkill
- pythonSkill
- reactSkill
- reviewSkill
- securitySkill
- swiper-migrationSkill
- ticket-refineSkill
- ticketSkill
- vueSkill
- wordpressSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

