Import and merge repository code and git history into an Nx workspace.
npx skills add https://github.com/Montte-erp/montte-nx --skill nx-import-montte-erp
Please help me install this Agent Skill. Skill: nx-import Source: https://github.com/Montte-erp/montte-nx/tree/main/.opencode/skills/nx-import Command: npx skills add https://github.com/Montte-erp/montte-nx --skill nx-import-montte-erp
This Skill helps developers and engineering teams import existing repositories into an Nx workspace while preserving commit history and minimizing post-merge friction. It addresses the common pain points of moving projects across repository boundaries including directory conflicts, missing root configuration, and mismatched tooling versions.
Use the nx-import skill to import a source repository into your workspace by specifying the source path and a destination (for example apps/my-app or libs/my-lib), preserve git history, then update pnpm workspace globs and root dependencies before running nx sync --yes.
High-intent search queries and answers about installing and using this skill.
To import repositories into an Nx monorepo while preserving git history, you move code into apps/ or libs/ directories while retaining full commit authorship. This process requires an empty destination directory to avoid conflicts during the merge.
Merging standalone repos into an Nx workspace is best handled by choosing between a subdirectory-at-a-time strategy for monorepo sources or a whole-repo import for single projects. This approach minimizes post-merge friction by addressing directory conflicts upfront.
After importing a repo into Nx, you update pnpm workspace configuration by modifying workspace globs to recognize the new apps/ or libs/ paths. You must also merge root package.json dependencies and run nx sync to ensure project references are correctly registered.
Fixing tsconfig and executor paths when moving libraries into an Nx monorepo involves updating TypeScript project references and adjusting build executor configurations. These post-import remediations ensure that newly imported apps and libs resolve correctly within the workspace.
Yes, when importing a new app, you need to register Nx plugins like @nx/eslint, @nx/jest, and @nx/vite. The import process includes detecting required tooling and applying practical fixes to ensure plugin configurations match existing workspace standards.
Yes, you can import a subdirectory from a monorepo source instead of the whole repository using the subdirectory-at-a-time strategy. This allows you to selectively move specific libraries or applications into your Nx workspace while still preserving their commit history.
tsparticlesImport code, projects, and Git history into an Nx workspace.
miordache93Import external repositories into an Nx monorepo with Git history.
pabloimrik17Discover and install Nx plugins for frameworks and tooling in an Nx workspace.
Cogni-AI-OUExtract a subdirectory's commit history using git-filter-branch and merge it into another repository.
