nx-workspace

Inspect Nx workspace projects, targets, and dependencies from nx show outputs.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/012e/thesis --skill nx-workspace-012e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-workspace
Source: https://github.com/012e/thesis/tree/main/.gemini/skills/nx-workspace
Command: npx skills add https://github.com/012e/thesis --skill nx-workspace-012e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nx workspace exploration helps teams quickly understand workspace structure, project configurations, and available targets to answer questions and plan changes without manual digging.

Core Features & Use Cases

  • Read workspace structure and list projects with nx show
  • Inspect project targets and configuration for planning, debugging, and impact assessment
  • Explore dependencies and affected projects to understand changes across the monorepo

Quick Start

Quickly summarize the workspace by asking for its projects, targets, and configuration details.

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 and targets in an Nx monorepo?

Inspect Nx workspace structure by parsing `nx show project --json` outputs and the Nx schema in node_modules, which reveals project configurations, targets, and dependencies for planning and debugging.

What is the best way to understand dependencies between apps and libs in an Nx workspace?

Understanding dependencies in an Nx workspace involves analyzing project configurations and affected projects to map how changes propagate across the monorepo's apps and libs for impact assessment.

Can I inspect project configurations in a typical Nx monorepo for debugging?

Yes, you can inspect Nx project configurations for debugging by relying on `nx show project --json` outputs and the Nx schema in node_modules to produce accurate, structured data for downstream processing.

How does an Nx workspace exploration tool handle impact assessment for changes?

Nx workspace impact assessment works by exploring dependencies and affected projects to understand how changes across the monorepo influence related apps and libs without manual digging.

Do I need the Nx schema in node_modules to accurately parse workspace structure?

Yes, the Nx schema in node_modules is required alongside `nx show project --json` outputs to accurately identify and understand the structure, projects, targets, and dependencies in an Nx workspace.