nx-import

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

3|2|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/storm-software/powerlines --skill nx-import-storm-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-import
Source: https://github.com/storm-software/powerlines/tree/main/.opencode/skills/nx-import
Command: npx skills add https://github.com/storm-software/powerlines --skill nx-import-storm-software

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of integrating existing code repositories or projects into an Nx monorepo, preserving history and ensuring compatibility.

Core Features & Use Cases

  • Repository Merging: Import code and Git history from external repositories into your Nx workspace.
  • Monorepo Adoption: Facilitate the transition of standalone projects or multiple repositories into a unified monorepo structure.
  • Use Case: You have a separate microservice repository and want to bring it into your main Nx monorepo to manage it alongside other services, maintaining its commit history.

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 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 migrate an external repository into an Nx workspace while preserving Git history?

Migrating an external repository into an Nx workspace while preserving Git history involves importing the codebase directly into your monorepo structure. This ensures the external project's commit logs remain intact during the repository migration.

Can I import only a specific subdirectory from a Git repository into my Nx monorepo?

Importing a specific subdirectory from a Git repository into your Nx monorepo is supported. This allows you to selectively migrate portions of an external project rather than bringing in the entire repository structure.

What is the best way to transition standalone projects into a unified Nx monorepo?

Transitioning standalone projects into a unified Nx monorepo is best handled by importing the repositories while adjusting project configurations. This approach maintains structure and ensures compatibility within the monorepo environment.

How do I handle ESLint, Jest, and TypeScript configuration adjustments when importing code into an Nx workspace?

Handling ESLint, Jest, and TypeScript configuration adjustments when importing code into an Nx workspace is part of the migration process. The integration automatically adjusts these settings to ensure seamless compatibility within the monorepo.

Does importing a microservice repository into an Nx workspace affect the existing project structure?

Importing a microservice repository into an Nx workspace preserves the existing project structure. The migration integrates the external code into a specified directory, maintaining the monorepo's overall organization and configuration.