Monorepo Skill

Why this skill exists

Monorepos done wrong become slower and harder to maintain than the polyrepos they replaced. This skill ensures monorepos are set up with correct build caching, clean dependency graphs, automated versioning, and CI pipelines that only rebuild what changed — so scale doesn't kill developer velocity.

---

0. Audit existing monorepo (if one exists)

# Detect monorepo tooling
cat package.json 2>/dev/null | python3 -c "
import json, sys
d = json.load(sys.stdin)
tools = []
all_deps = {**d.get('dependencies',{}), **d.get('devDependencies',{})}
if 'nx' in all_deps: tools.append('Nx')
if 'turbo' in all_deps or 'turborepo' in all_deps: tools.append('Turborepo')
if 'lerna' in all_deps: tools.append('Lerna (legacy)')
if d.get('workspaces'): tools.append(f\"npm/yarn workspaces: {d['workspaces']}\")
print('Monorepo tools:', tools or ['none detected'])
"

cat pnpm-workspace.yaml 2>/dev/null && echo "pnpm workspace found"
ls nx.json turbo.json lerna.json 2>/dev/null

# List all packages/apps
find . -name "package.json" \
  | grep -v "node_modules\|dist\|build\|coverage" \
  | xargs grep -l '"name"' \
  | while read f; do
    name=$(python3 -c "import json; d=json.load(open('$f')); print(d.get('name','?'))")
    echo "$name  ($f)"
  done | sort

# Package dependency graph
npx nx graph 2>/dev/null &   # opens browser
turbo run build --dry=json 2>/dev/null | python3 -m json.tool | head -60