nx-import

Import code and Git history from source repositories into an Nx workspace.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ankitgahlyan/webapp --skill nx-import-ankitgahlyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/ankitgahlyan/webapp/tree/main/.gemini/skills/nx-import
Command: npx skills add https://github.com/ankitgahlyan/webapp --skill nx-import-ankitgahlyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of integrating existing codebases into an Nx monorepo, preserving history and ensuring seamless project migration.

Core Features & Use Cases

  • Repository Merging: Import code and Git history from external repositories into your Nx workspace.
  • Monorepo Adoption: Facilitate the transition to a monorepo architecture by consolidating projects.
  • Use Case: You have a separate repository for your UI components and want to bring it into your main application's Nx monorepo. This Skill handles the import, maintaining commit history and project structure.

Quick Start

Use the nx-import skill to import the code from the '/path/to/source/repo' directory into the 'apps/new-app' 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 while preserving Git history?

Use the `nx import` command to merge code and commit logs from a source repository directory into your Nx workspace, ensuring Git history is preserved during monorepo consolidation.

What is the best way to consolidate multiple projects into a single Nx workspace?

The best way to consolidate multiple projects into a single Nx workspace is using `nx import` to migrate codebases while resolving directory conventions, app vs. library detection, and dependency management.

Can I migrate separate UI components into my main Nx monorepo application?

Yes, you can migrate separate UI components into your main Nx monorepo by running `nx import` to bring the source repository directory into a target workspace path like 'apps/new-app', maintaining project structure.

Does importing code into an Nx workspace handle application versus library detection?

Yes, importing code into an Nx workspace handles app vs. library detection, addressing directory conventions and structural challenges during the project migration and codebase consolidation process.

What are the limitations of using nx import for repository migration?

Limitations of using `nx import` for repository migration include resolving directory conventions, managing dependencies, and ensuring correct app vs. library detection during codebase consolidation into the monorepo.