Monorepo Dependency Graph

Your monorepo has 15 packages. You refactor @org/utils. Three CI pipelines fail. You didn't know @org/auth imported @org/utils which imported @org/config which imported @org/auth.

This skill maps every internal dependency edge, detects circular imports, finds orphaned packages nobody uses, and flags packages that have too many dependents — the ones that become a bottleneck for every team.

Works by reading package.json/Cargo.toml/go.mod — no install required. Zero external API.

Trigger Phrases

• "monorepo deps", "workspace dependencies"
• "which packages depend on X", "impact of changing X"
• "circular dependency in monorepo"
• "orphaned package", "unused internal package"
• "coupling analysis", "dependency graph"
• "pnpm workspace", "yarn workspaces", "cargo workspace"
• "/mono-deps"