技能详情（站内镜像，无评论）
作者：Alireza Rezvani @alirezarezvani
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 155 · 2 current installs · 2 all-time installs
⭐ 0
安装量（当前） 2
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：alirezarezvani/monorepo-navigator
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill's instructions, scope, and examples are coherent with a monorepo navigation/management tool; no unrelated credentials, installs, or hidden endpoints are requested, though it includes powerful repo-changing commands and references optional cache tokens you should be careful with.
目的
The name/description (monorepo tooling) matches the content: Turborepo, Nx, pnpm, changesets, dependency-graph generation, migration steps, CI patterns, and CLAUDE.md guidance are all within the stated purpose. The SKILL.md does reference remote-cache tokens (TURBO_TOKEN, TURBO_TEAM) and DATABASE_URL in example configs, which are relevant to CI/remote-cache setup for monorepos; their mention is appropriate for this domain even though the skill…
说明范围
The instructions include shell commands and example scripts that will read and write repository files, run Node (execSync), generate files, perform git operations (git clone, git filter-repo, git merge --allow-unrelated-histories), and contact remote services (Vercel/turbo remote cache, GitHub). These are expected for migration and build tooling, but some operations are destructive (git filter-repo rewrites history, merges with allow-unrelated…
安装机制
Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. Example scripts are provided for users to run themselves; the skill does not perform installs automatically.
证书
The SKILL.md references environment variables that are reasonable for CI and remote caching (TURBO_TOKEN, TURBO_TEAM, TURBO_API, NODE_ENV, DATABASE_URL). The skill metadata does not declare required env vars, which is acceptable for an instruction-only guide, but users should be aware examples assume those variables may exist and be used by the commands. No unrelated third-party credentials are requested.
持久
The skill is not always-enabled, is user-invocable, has no install actions, and does not request persistent platform privileges. It does not modify other skills' configs or platform-wide settings.
综合结论
This is a coherent, instruction-only monorepo guide. Before running anything from it: 1) review any commands that rewrite git history (git filter-repo) and make backups (clone, create tags, or mirror the repo) — those commands are destructive if misused; 2) inspect any example scripts that execute shell commands (the Node execSync example) before running them in your workspace; 3) remote cache configuration mentions TURBO_TOKEN / TURBO_TEAM / …
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「monorepo-navigator」。简介：Monorepo Navigator。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/alirezarezvani/monorepo-navigator/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: "monorepo-navigator"
description: "Monorepo Navigator"
---
# 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
| Tool | Best For | Key Feature |
|---|---|---|
| **Turborepo** | JS/TS monorepos, simple pipeline config | Best-in-class remote caching, minimal config |
| **Nx** | Large enterprises, plugin ecosystem | Project graph, code generation, affected commands |
| **pnpm workspaces** | Workspace protocol, disk efficiency | `workspace:*` for local package refs |
| **Lerna** | npm publishing, versioning | Batch publishing, conventional commits |
| **Changesets** | Modern 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
## Common Pitfalls
| Pitfall | Fix |
|---|---|
| Running `turbo run build` without `--filter` on every PR | Always use `--filter=...[origin/main]` in CI |
| `workspace:*` refs cause publish failures | Use `pnpm changeset publish` — it replaces `workspace:*` with real versions automatically |
| All packages rebuild when unrelated file changes | Tune `inputs` in turbo.json to exclude docs, config files from cache keys |
| Shared tsconfig causes one package to break all type-checks | Use `extends` properly — each package extends root but overrides `rootDir` / `outDir` |
| git history lost during migration | Use `git filter-repo --to-subdirectory-filter` before merging — never move files manually |
| Remote cache not working in CI | Check TURBO_TOKEN and TURBO_TEAM env vars; verify with `turbo run build --summarize` |
| CLAUDE.md too generic — Claude modifies wrong package | Add 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