nx-import

Import external repositories into an Nx monorepo with Git history.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/miordache93/evoklas --skill nx-import-miordache93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/miordache93/evoklas/tree/main/.cursor/skills/nx-import
Command: npx skills add https://github.com/miordache93/evoklas --skill nx-import-miordache93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of migrating existing code repositories or projects into an Nx monorepo, preserving history and ensuring a smooth transition.

Core Features & Use Cases

  • Monorepo Adoption: Integrate code from separate repositories into a unified Nx workspace.
  • Project Migration: Move individual projects or entire codebases into an existing Nx monorepo.
  • History Preservation: Ensures that the commit history of the imported code is maintained within the monorepo.
  • Use Case: You have a legacy project in its own Git repository and want to bring it into your company's main Nx monorepo to benefit from shared tooling and dependencies.

Quick Start

Use the nx-import skill to import the source repository located at '/path/to/source' into the 'apps/web' directory of the current 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 an existing repository into an Nx monorepo?

To import an existing repository into an Nx monorepo, use the nx import command to merge external repositories or subdirectories. This migrates the project while preserving Git history and managing dependency resolution.

Does importing a project into an Nx monorepo preserve Git commit history?

Yes, importing a project into an Nx monorepo preserves Git commit history. The import process ensures that the commit history of the migrated code is maintained within the target Nx workspace.

How do I handle dependency resolution and configuration merging when migrating to an Nx monorepo?

Dependency resolution and configuration merging are handled automatically as critical post-import tasks. The process updates TypeScript project references and manages diverse package manager configurations during the repository migration.

Can I migrate a subdirectory instead of a full repository into my Nx workspace?

Yes, you can migrate a subdirectory instead of a full repository. The nx import command supports merging external subdirectories into an existing Nx monorepo, adapting to diverse source structures.

What are the limitations of using the nx import command for monorepo adoption?

Limitations of using nx import for monorepo adoption involve potential complexities with diverse source structures and varying package manager configurations. Challenges may arise during configuration merging and TypeScript project reference updates across different imported projects.