nx-import

Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

Install
npx skills add 'https://github.com/nrwl/nx/tree/master/.agents/skills/nx-import'
Download bundle ↓
master · 646e806Scanned 2026-09-17

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗
View on GitHub
← Back to SKILL.md

Gradle

  • If you import an entire Gradle repository into a subfolder, files like gradlew, gradlew.bat, and gradle/wrapper will end up inside that imported subfolder.
  • The @nx/gradle plugin expects those files at the workspace root to infer Gradle projects/tasks automatically.
  • If the target workspace has no Gradle setup yet, consider moving those files to the root (especially when using @nx/gradle).
  • If the target workspace already has Gradle configured, avoid duplicate wrappers: remove imported duplicates from the subfolder or merge carefully.
  • Because the import lands in a subfolder, Gradle project references can break; review settings and project path references, then fix any errors.
  • If @nx/gradle is installed, run nx show projects to verify that Gradle projects are being inferred.

Helpful docs:

Referenced from SKILL.md