Author first-party Nx migrations with generators, prompts, and packageJsonUpdates entries.
npx skills add https://github.com/nrwl/nx --skill author-migration
Please help me install this Agent Skill. Skill: author-migration Source: https://github.com/nrwl/nx/tree/main/.claude/skills/author-migration Command: npx skills add https://github.com/nrwl/nx --skill author-migration
When Nx removes, renames, or deprecates an option, executor, or dependency, existing workspaces can break on nx migrate unless a proper migration ships with the change. This Skill guides the authoring of correct first-party Nx migrations so upgrades do not silently break user workspaces.
requires semantics, packageJsonUpdates groups, and the colocated update-VER/NAME.{ts,spec.ts,md} file layout.nx migrate actually consumes each key, plus a registry of deprecated patterns to never copy.Ask the assistant to author an Nx migration for a breaking change, specifying the affected package and the target release train.
High-intent search queries and answers about installing and using this skill.
Classify each breaking item into a treatment: declarative packageJsonUpdates for plain bumps, a generator implementation for deterministic source transforms, or a prompt .md for judgment-based changes. Then wire a generators entry in migrations.json with version, implementation, and documentation keys.
Use a prompt only when no subset of the change is safely automatable by a deterministic transform. If any mechanical part exists, ship a hybrid entry with both implementation and prompt keys, since generators run for every user while prompts only execute in agentic flows.
An entry runs when installed version is strictly less than the entry version and the entry version is at most the target, with prerelease ordering. Always use the train's exact next prerelease, never a bare final version or a backdated prerelease.
Generators entries run code or prompts against the workspace tree, while packageJsonUpdates groups declaratively bump dependency versions. Groups gate on the source major window with inclusive installed-side bounds and are evaluated in key order to support multi-major chains.
Skips usually come from a wrong requires gate: it evaluates against the version the package lands on in the same run, and a package absent from both pending updates and installed deps fails the gate. Upper bounds that encode the source window also fail when the run bumps past the cap.
No. The runner silently discards GeneratorCallback returns and installs packages by diffing package.json itself. Migrations return void, a string array of next steps, or an object with nextSteps, agentContext, and skipAgentic.
breakcafeMerge upstream NanoClaw updates into customized Git forks with preflight checks and rollback.
tech-leads-clubRun Nx workspace-plugin generators with dry-run, formatting, and test checks.
hamza-sahinUpgrade Capacitor plugins across major versions with dependency and native updates.
ClogogoDiscover and install Nx plugins for an Nx workspace.