Monorepo Navigator

alirezarezvani/claude-skills/engineering/skills/monorepo-navigator

by alirezarezvani19392f7a0826No license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

Navigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Cross-package impact analysis, selective builds/tests on affected packages, remote caching, dependency graph visualization, and structured multi-repo to monorepo migrations. Use when setting up a new monorepo, optimizing CI for a large workspace, debugging cross-package dependency issues, or planning a multi-repo consolidation.

AI-generated overview

Guides monorepo setup, tooling, CI optimization, and multi-repo migration, with a script that analyzes workspace structure.

What it does
Provides guidance for navigating, managing, and optimizing monorepos built with Turborepo, Nx, pnpm workspaces, and Lerna. It covers cross-package impact analysis, selective builds and tests for affected packages, remote caching, dependency graph visualization, publishing with changesets, and multi-repo to monorepo migration. It also ships a Python analyzer script that inspects a monorepo path and can emit JSON output, plus reference documents on patterns and tooling.
When to use it
Use when several packages or apps share code and need unified tooling, when builds are slow because everything rebuilds on any change, when consolidating multiple repositories into one, or when publishing packages with coordinated versioning.
Requirements
Python 3 to run scripts/monorepo_analyzer.py; the skill ships executable scripts and reference documents. Remote caching guidance refers to TURBO_TOKEN and TURBO_TEAM environment variables, and publishing guidance refers to npm and pnpm changeset workflows.

Monorepo Navigator

Tier: POWERFUL
Category: Engineering
Domain: Monorepo Architecture / Build Systems


Overview

Navigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds/tests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration for workspace-aware development.


Core Capabilities

  • Cross-package impact analysis — determine which apps break when a shared package changes
  • Selective commands — run tests/builds only for affected packages (not everything)
  • Dependency graph — visualize package relationships as Mermaid diagrams
  • Build optimization — remote caching, incremental builds, parallel execution
  • Migration — step-by-step multi-repo → monorepo with zero history loss
  • Publishing — changesets for versioning, pre-release channels, npm publish workflows
  • Claude Code config — workspace-aware CLAUDE.md with per-package instructions

When to Use

Use when:

  • Multiple packages/apps share code (UI components, utils, types, API clients)
  • Build times are slow because everything rebuilds when anything changes
  • Migrating from multiple repos to a single repo
  • Need to publish packages to npm with coordinated versioning
  • Teams work across multiple packages and need unified tooling

Skip when:

  • Single-app project with no shared packages
  • Team/project boundaries are completely isolated (polyrepo is fine)
  • Shared code is minimal and copy-paste overhead is acceptable

Tool Selection

ToolBest ForKey Feature
TurborepoJS/TS monorepos, simple pipeline configBest-in-class remote caching, minimal config
NxLarge enterprises, plugin ecosystemProject graph, code generation, affected commands
pnpm workspacesWorkspace protocol, disk efficiencyworkspace:* for local package refs
Lernanpm publishing, versioningBatch publishing, conventional commits
ChangesetsModern versioning (preferred over Lerna)Changelog generation, pre-release channels

Most modern setups: pnpm workspaces + Turborepo + Changesets


Turborepo

→ See references/monorepo-tooling-reference.md for details

Workspace Analyzer

bash
python3 scripts/monorepo_analyzer.py /path/to/monorepopython3 scripts/monorepo_analyzer.py /path/to/monorepo --json

Also see references/monorepo-patterns.md for common architecture and CI patterns.

Common Pitfalls

PitfallFix
Running turbo run build without --filter on every PRAlways use --filter=...[origin/main] in CI
workspace:* refs cause publish failuresUse pnpm changeset publish — it replaces workspace:* with real versions automatically
All packages rebuild when unrelated file changesTune inputs in turbo.json to exclude docs, config files from cache keys
Shared tsconfig causes one package to break all type-checksUse extends properly — each package extends root but overrides rootDir / outDir
git history lost during migrationUse git filter-repo --to-subdirectory-filter before merging — never move files manually
Remote cache not working in CICheck TURBO_TOKEN and TURBO_TEAM env vars; verify with turbo run build --summarize
CLAUDE.md too generic — Claude modifies wrong packageAdd explicit "When working on X, only touch files in apps/X" rules per package CLAUDE.md

Best Practices

  1. Root CLAUDE.md defines the map — document every package, its purpose, and dependency rules
  2. Per-package CLAUDE.md defines the rules — what's allowed, what's forbidden, testing commands
  3. Always scope commands with --filter — running everything on every change defeats the purpose
  4. Remote cache is not optional — without it, monorepo CI is slower than multi-repo CI
  5. Changesets over manual versioning — never hand-edit package.json versions in a monorepo
  6. Shared configs in root, extended in packages — tsconfig.base.json, .eslintrc.base.js, jest.base.config.js
  7. Impact analysis before merging shared package changes — run affected check, communicate blast radius
  8. Keep packages/types as pure TypeScript — no runtime code, no dependencies, fast to build and type-check

Source and attribution

Source:alirezarezvani/claude-skillsinengineering/skills/monorepo-navigatorat commit19392f7

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Monorepo Navigator · engineering/skills/monorepo-navigator Agent Skill | SourceWeft