nx-workspace

Inspect Nx workspace projects, targets, and dependency graphs using nx CLI commands.

3|10|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fleetshift/fleetshift-poc --skill nx-workspace-fleetshift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-workspace
Source: https://github.com/fleetshift/fleetshift-poc/tree/main/.agents/skills/nx-workspace
Command: npx skills add https://github.com/fleetshift/fleetshift-poc --skill nx-workspace-fleetshift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers working in Nx monorepos often struggle to answer basic questions about project structure, available targets, and dependency relationships without digging through scattered configuration files. This Skill provides read-only exploration of Nx workspaces using structured CLI commands. ## Core Features & Use Cases - Project Discovery: List and filter projects by name, glob pattern, tag, type, or target using nx show projects. - Configuration Inspection: Retrieve fully resolved project configuration (including plugin-inferred targets) via nx show project --json instead of reading partial project.json files. - Dependency Analysis: Query the project graph with nx graph --print and jq to find what depends on a given library. - Troubleshooting: Diagnose errors like "Cannot find configuration for task" and stale workspace cache issues. - Use Case: When an nx build command fails, use this Skill to check which targets actually exist on the project and how they are configured before retrying. ## Quick Start Ask the AI to list all projects in this Nx workspace and show the build target configuration for a specific project.

Frequently Asked Questions about nx-workspace

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

FAQPage Schema
How do I list all projects in an Nx workspace?

Run `nx show projects` to list every project in the workspace. Add `--json` for machine-readable output, or filter with `--projects` using glob patterns, tags like `tag:publishable`, or negation like `!*-e2e`.

How to find what depends on a library in Nx?

Use `nx graph --print` to output the project graph as JSON, then pipe it to jq: select dependency entries whose target matches the library name. This returns all projects that depend on that library.

Why should I use nx show project instead of reading project.json?

The project.json file only contains partial configuration. `nx show project <name> --json` returns the fully resolved configuration, including targets inferred by Nx plugins, giving you the complete picture of available tasks.

How do I fix 'Cannot find configuration for task' in Nx?

First check which targets exist with `nx show project X --json | jq '.targets | keys'`. Then verify which projects have that target using `nx show projects --withTarget <target>` to confirm the task is defined where you expect.

How do I find affected projects in an Nx monorepo?

Run `nx show projects --affected` to detect projects changed relative to your base branch. You can specify `--base=main`, compare commits with `--base` and `--head`, or include uncommitted changes with `--uncommitted`.