Monorepo Navigator

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

作者 alirezarezvani19392f7a0826无许可证27K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库5周前更新

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 生成的概览

指导 monorepo 的搭建、工具选型、CI 优化与多仓库迁移,并提供分析工作区结构的脚本。

功能
提供针对 Turborepo、Nx、pnpm workspaces 和 Lerna 构建的 monorepo 的导航、管理与优化指导。内容涵盖跨包影响分析、仅对受影响包执行构建与测试、远程缓存、依赖图可视化、使用 changesets 发布,以及从多仓库迁移到 monorepo。它还附带一个 Python 分析脚本,可检查 monorepo 路径并输出 JSON,以及关于模式与工具链的参考文档。
适用场景
适用于多个包或应用共享代码并需要统一工具链时,任何改动都会导致全部重新构建而拖慢构建时,将多个仓库合并为一个时,或需要协调版本号发布包时。
运行要求
需要 Python 3 来运行 scripts/monorepo_analyzer.py;该技能附带可执行脚本和参考文档。远程缓存相关内容涉及 TURBO_TOKEN 和 TURBO_TEAM 环境变量,发布相关内容涉及 npm 与 pnpm changeset 工作流。

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

来源与署名

来源:alirezarezvani/claude-skills位于engineering/skills/monorepo-navigator提交19392f7

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架