nx-import

Import existing repositories into Nx workspaces while preserving git history.

Updated May 14, 2026
One-click install
npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill nx-import-chroniicallydiistracted
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.opencode/skills/nx-import
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill nx-import-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of adopting Nx across multiple existing repositories by providing a structured, low-surprise process to import apps and libraries into an Nx workspace while preserving functionality and git history.

Core Features & Use Cases

  • Guided monorepo adoption with nx import: Brings code from a source repo into an Nx workspace using the nx import workflow and the recommended directory-at-a-time strategy.
  • Import planning and conflict avoidance: Helps you choose the correct destination paths, avoid directory/name collisions, and respect Nx conventions so the imported projects are discoverable and runnable.
  • Post-import repair checklist: Addresses common migration failures like pnpm workspace glob issues, root config gaps (nx.json/tsconfig/eslint/jest), and TypeScript noEmit/project reference incompatibilities.

Use case example: You want to move several existing frontend and shared library repos into a single Nx monorepo so teams can share tooling and run consistent targets like build, test, and lint.

Quick Start

Tell the assistant: “Import my existing repository into an Nx workspace using nx import, preserving git history and ensuring pnpm, tsconfig, and lint/test targets work after import.”

Frequently Asked Questions about nx-import

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

FAQPage Schema
How do I migrate an existing repository into an Nx monorepo while preserving git history?

To migrate existing repositories into an Nx monorepo while preserving git history, use the nx import workflow with a directory-at-a-time strategy. This brings source code into apps/* and packages/* or libs/* while maintaining commit history and workspace conventions.

What is the best way to avoid directory collisions when importing projects into Nx?

The best way to avoid directory collisions during an Nx monorepo migration is to plan destination paths carefully and respect Nx conventions before importing. Choosing correct destination directories prevents name collisions and ensures projects are discoverable within the workspace.

How do I fix pnpm workspace and TypeScript configuration issues after an Nx import?

To fix pnpm workspace and TypeScript configuration issues after an Nx import, apply a post-import repair checklist addressing root config gaps. This resolves common migration failures like pnpm workspace glob issues, TypeScript noEmit incompatibilities, and project reference gaps for deterministic setups.

Can I import multiple frontend and shared library repos into a single Nx workspace?

Yes, you can import multiple frontend and shared library repos into a single Nx workspace using nx import. This allows teams to share tooling and run consistent targets like build, test, and lint across all imported apps and libraries.

Why does ESLint or Jest integration break after moving code into an Nx workspace?

ESLint or Jest integration breaks after moving code into an Nx workspace due to root config gaps and missing project references. Resolving these common migration failures requires applying post-import fixes to align workspace conventions and ensure deterministic reproducible setups.