nx-monorepo

Manages Nx workspaces with project graphs, affected detection, code generation, and caching.

9|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill nx-monorepo-abdullahmalik17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nx-monorepo
Source: https://github.com/AbdullahMalik17/Hacathan_5/tree/main/.claude/skills/nx-monorepo
Command: npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill nx-monorepo-abdullahmalik17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing a large monorepo with many interdependent JavaScript, TypeScript, and Python projects is slow and error-prone without proper tooling. This Skill provides expert guidance for Nx workspace operations so you can build, test, and lint only what changed instead of the entire repository. ## Core Features & Use Cases - Project Graph Analysis: Visualize and query project dependencies with nx graph to understand how apps and libraries connect. - Affected Detection: Run builds, tests, and lints only on projects impacted by a change using nx affected, dramatically speeding up CI pipelines. - Code Generation & Caching: Scaffold new Next.js, React, Node, or Python (uv) projects with generators, and accelerate repeated tasks with local and Nx Cloud remote caching. - Use Case: After modifying a shared UI library, run nx affected -t test to execute tests only for the apps that depend on it, then connect Nx Cloud so your whole team shares the build cache. ## Quick Start Ask the assistant to show which projects are affected by your current changes and run their tests using Nx.

Frequently Asked Questions about nx-monorepo

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

FAQPage Schema
How do I run tests only for changed projects in an Nx monorepo?▼

Use nx affected -t test to run tests only for projects impacted by your changes. Add --base=origin/main --head=HEAD to compare against a specific branch, which is the standard pattern for CI pipelines.

How to visualize project dependencies in an Nx workspace?▼

Run nx graph to open an interactive dependency graph in your browser. Use nx graph --focus=my-app to inspect one project's dependencies, or nx graph --file=output.json to export the graph as JSON for programmatic analysis.

Can Nx manage Python projects alongside JavaScript apps?▼

Yes, Python projects use uv workspaces for dependency management with a manual project.json file so Nx can orchestrate their build, test, and lint targets. A single uv.lock at the root manages all Python dependencies while Nx handles task execution.

Does Nx caching work across team members and CI?▼

Local caching works automatically for cacheable targets, but sharing requires Nx Cloud. Connect with npx nx connect, after which remote cache hits let teammates and CI skip tasks already computed elsewhere.

Why is my Nx cache not working for a build target?▼

Verify the target is marked cacheable in the targetDefaults section of nx.json and that its inputs are stable. Run the build with --verbose to inspect input hashing, and use nx reset to clear a corrupted cache.