Monorepo Rules

The problem

Monorepos often collapse under their own weight when package boundaries blur and dependency cycles emerge. You end up with 20-minute CI pipelines for one-line changes because the build tool cannot determine what is actually affected.

What it does

• Enforces package boundaries by detecting relative imports that bypass the workspace graph.
• Audits turbo.json task pipelines to fix cache misses caused by missing inputs, outputs, or undeclared env variables.
• Identifies and breaks circular dependencies that prevent independent package builds and caching.
• Generates step-by-step plans for cross-package refactors and codemods to move symbols without breaking importers.
• Optimizes CI configurations to correctly detect affected packages using merge-base comparisons.

Frameworks & tools

Designed for Turborepo and pnpm workspaces. Works with TypeScript, Next.js, and ESLint.

Why this beats prompting it yourself

Standard LLMs often suggest relative path fixes that compile but break monorepo isolation. This skill uses a strict trigger matrix to prioritize architectural integrity, like breaking cycles before fixing cache issues, ensuring your workspace remains scalable.

Use cases

• Fixing a "cache never hits" issue in Turborepo by auditing environment variables.
• Extracting shared logic into a new workspace package without breaking the build.
• Reducing CI times by implementing merge-base filtering for affected packages.
• Mapping out a dependency graph to find and resolve complex circular imports.

Known limitations

Does not execute turbo commands, publish packages, or modify CI secrets. It provides configuration edits and CLI commands for the user to run manually.