nx-import

Import external repositories into an Nx workspace while preserving git history.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/AyalaKaguya/hermes-swarm --skill nx-import-ayalakaguya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/AyalaKaguya/hermes-swarm/tree/main/.opencode/skills/nx-import
Command: npx skills add https://github.com/AyalaKaguya/hermes-swarm --skill nx-import-ayalakaguya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the complexity of adopting Nx monorepo architecture by automating the migration of existing projects, preserving git history, and resolving configuration conflicts.

Core Features & Use Cases

  • Project Import: Safely move applications and libraries into an Nx workspace while maintaining commit history.
  • Dependency Resolution: Automatically identifies and helps merge root dependencies, plugins, and workspace configurations.
  • Use Case: When migrating a legacy repository into a new monorepo, use this Skill to handle the directory mapping, plugin registration, and TypeScript path adjustments required to keep the build pipeline functional.

Quick Start

Use the nx-import skill to import the project located in the source folder into the apps 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 migrate a repository into an Nx monorepo while preserving git history?

Migrating a repository into an Nx monorepo while preserving git history involves importing the external project structure into your workspace and resolving directory mappings and configuration conflicts to ensure the build pipeline remains functional.

How do I resolve TypeScript project references when importing apps into an Nx workspace?

Resolving TypeScript project references during an Nx workspace import requires adjusting TypeScript path mappings and glob patterns to ensure compatibility with the Nx plugin architecture and maintain build pipeline functionality.

Can I import a subdirectory of a repository into an existing Nx workspace?

Yes, you can import a subdirectory of an external repository into an existing Nx workspace, facilitating the migration of specific applications and libraries while adjusting the directory mapping and ESLint configurations.

What is the best way to manage root dependencies when adopting an Nx monorepo architecture?

Adopting an Nx monorepo architecture requires automatically identifying and merging root dependencies, plugins, and workspace configurations to resolve conflicts during the external project import process.

Does importing a legacy repository into an Nx workspace affect Jest and ESLint configurations?

Importing a legacy repository into an Nx workspace ensures compatibility by resolving and adjusting ESLint and Jest configurations alongside TypeScript paths during the project migration process.