nx-import

Import and merge external repositories into an Nx workspace while preserving commit history.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/iqbal125/typescript_projects --skill nx-import-iqbal125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/iqbal125/typescript_projects/tree/main/nestjs-react-monorepo-nx/.agents/skills/nx-import
Command: npx skills add https://github.com/iqbal125/typescript_projects --skill nx-import-iqbal125

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Import, merge, or consolidate multiple repositories into a single Nx workspace while preserving commit history and aligning projects to Nx conventions.

Core Features & Use Cases

  • Import projects and libraries from source repositories into the current Nx workspace, preserving git histories.
  • Resolve architecture and path conflicts by applying an import strategy (subdirectory-at-a-time or whole-repo) to maintain consistent workspace structure.
  • Use cases include adopting Nx across multiple repos, moving code into a monorepo, or bringing code and history from another repository.

Quick Start

Run nx import with the source and destination paths to begin integrating a repository into your Nx workspace.

Frequently Asked Questions about nx-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import and merge multiple repositories into an Nx workspace?▼

To import repositories into an Nx workspace, run the import command with source and destination paths to integrate projects while preserving git history and aligning to workspace conventions.

Can I migrate code into a monorepo without losing git commit history?▼

Yes, you can migrate code into a monorepo while preserving commit history. The import process ensures a traceable migration by syncing histories during the repository integration.

What is the best way to resolve path conflicts when consolidating repos into an Nx workspace?▼

The best way to resolve path conflicts is by applying an import strategy, either subdirectory-at-a-time or whole-repo, to maintain a consistent workspace structure and project boundaries.

When do I need to use an import strategy for adopting Nx across multiple repositories?▼

You need an import strategy when adopting Nx across multiple repositories, moving code into a monorepo, or syncing histories during integration to ensure consistent and traceable migration.

Does merging external projects into an Nx workspace affect existing project boundaries?▼

Merging external projects enforces documented workspace conventions and project boundaries. The integration applies a specific import strategy to prevent architecture conflicts during consolidation.