Import repositories into an Nx workspace while preserving git history.
npx skills add https://github.com/G9000/animaOS-SWARM --skill nx-import-g9000
Please help me install this Agent Skill. Skill: nx-import Source: https://github.com/G9000/animaOS-SWARM/tree/main/.agents/skills/nx-import Command: npx skills add https://github.com/G9000/animaOS-SWARM --skill nx-import-g9000
Importing repositories into an Nx workspace is error-prone and involves many manual fixes: preserving git history, avoiding directory conflicts, merging root dependencies and Nx configuration, updating pnpm workspace globs, and repairing TypeScript, ESLint, and testing setups after import. This Skill documents the recommended strategies, gotchas, and fix order required to reliably adopt Nx across single-project repos and multi-project monorepos.
Import the source repository into this workspace with nx import, preserve git history, and then reconcile root dependencies, pnpm workspace globs, and nx.json targetDefaults.
High-intent search queries and answers about installing and using this skill.
Use the nx import command to bring code and commit history into the destination Nx workspace. It handles subdirectory and whole-repo imports while preserving the original directory structure.
The best way to merge root dependencies and nx.json settings is to reconcile them after the import. You must also fix pnpm workspace globs and resolve any dependency version conflicts to ensure the monorepo functions correctly.
To fix TypeScript project references and executor paths after moving projects into a monorepo, use nx sync and nx reset. These commands update the references and repair executor configurations for the newly imported projects.
Yes, you can import a subdirectory from a single-project repo instead of the whole repository. The import strategy offers guidance for subdirectory-at-a-time imports versus whole-repo imports and when to use each approach.
Importing a repository into an Nx monorepo breaks pnpm workspace globs because the relative paths change during the move. The Skill provides steps to repair these globs alongside resolving project name collisions and frontend tsconfig base settings.
Yes, the Nx import process handles plugin detection and installation for ESLint, Jest, Vite, Next.js, Gradle, and Turborepo migrations. It adjusts tooling setups to function correctly within the new workspace environment.
withzombiesSplit, merge, and rewire bd tasks while preserving change history.
pantheon-orgDesign and implement reusable Nx executors for TypeScript monorepos.
wahidyankfConsolidate separate code repositories into a single Nx monorepo while preserving git history.
MovchanetsImport and merge repositories into an Nx workspace while preserving history.
