nx-import

Import and merge repositories into an Nx workspace while preserving history.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill nx-import-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/nx-import
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill nx-import-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork from adopting Nx by helping you bring existing repositories, projects, and histories into a workspace without breaking builds, tests, or configuration conventions.

Core Features & Use Cases

  • Repository Import Planning: Distinguishes application and library sources, chooses the right destination layout, and avoids common monorepo conflicts.
  • Workspace Repair Guidance: Identifies and fixes issues around pnpm workspace globs, root dependencies, TypeScript references, ESLint, Jest, Vite, Next.js, and Gradle imports.
  • Migration Use Case: A team consolidating multiple frontend and backend repos can use this Skill to move each project into the correct apps or libraries folder while preserving history and keeping targets working.
  • Post-Import Validation: Helps verify target inference, config alignment, and environment-specific requirements after the migration is complete.

Quick Start

Ask the skill to analyze a repository and produce an Nx import plan for moving its projects into 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 existing repositories into an Nx monorepo without breaking builds?

Migrating repositories into an Nx monorepo requires planning project layouts, distinguishing application and library destinations, and fixing configuration conflicts for TypeScript, ESLint, and Jest to preserve builds and history during workspace import.

Can I consolidate multiple frontend and backend repositories into a single Nx workspace?

Consolidating multiple frontend and backend repositories into a single Nx workspace is supported by moving each project into the correct apps or libraries folders while preserving Git history and keeping target configurations working.

What is the best way to fix pnpm workspace globs and TypeScript references after a repository migration?

Fixing pnpm workspace globs and TypeScript references after a repository migration involves identifying workspace repair issues and applying configuration alignment to ensure root dependencies and project targets map correctly in the new Nx layout.

Does the Nx import workflow support migrating projects from Gradle and Turborepo sources?

The Nx import workflow supports migrating projects from Gradle and Turborepo sources by handling source-specific configuration fixes and validating target inference to ensure environment-specific requirements are met post-import.

Why do my Jest and Vite configurations break after importing projects into an Nx workspace?

Jest and Vite configurations break after importing projects into an Nx workspace due to misaligned root dependencies and missing workspace repair steps, requiring post-import validation to ensure config alignment and target inference.

How do I validate target inference and config alignment after completing an Nx repository import?

Validating target inference and config alignment after an Nx repository import involves post-import checks that verify environment-specific requirements, ensure correct project destinations, and confirm that application and library targets function properly.