nx-import

Import external repositories into an Nx workspace with Git history.

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

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 workspace, ensuring a smooth transition and preserving project history.

Core Features & Use Cases

  • Monorepo Adoption: Facilitates the adoption of Nx for managing multiple projects within a single monorepo.
  • Code Migration: Enables importing code and commit history from external repositories or directories into an existing Nx workspace.
  • Use Case: You have a separate repository for your UI components and want to bring it into your main Nx monorepo to manage them together. This skill will guide you through the nx import process.

Quick Start

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

To import a repository into an Nx monorepo while preserving Git history, use the `nx import` command to merge external code repositories or subdirectories into your existing Nx workspace.

What is the best way to migrate a separate UI components repository into my main Nx workspace?

Migrating a separate UI components repository into a main Nx workspace is best handled by the `nx import` command, which streamlines monorepo adoption and integrates external project code into a target directory.

Does the Nx import command work with specific technology setups like Next.js, Vite, and Jest?

Yes, the Nx import process requires careful handling of technology-specific setups like Next.js, Vite, and Jest, alongside managing TypeScript project references and ESLint configurations during integration.

How do I handle pnpm workspace globs and root dependencies when importing code into Nx?

Handling pnpm workspace globs and root dependencies during an Nx import requires careful configuration adjustments to ensure the merged external code repository functions correctly within the existing Nx workspace.

Can I import a subdirectory from an external code repository instead of the entire project into Nx?

Yes, you can import a subdirectory from an external code repository into an existing Nx workspace using the `nx import` command, which supports merging specific project paths rather than whole repositories.

What challenges should I anticipate during monorepo adoption and code migration with Nx?

During monorepo adoption and code migration with Nx, anticipate challenges related to preserving Git history, resolving root dependencies, adjusting pnpm workspace globs, and aligning ESLint configurations.