What problem does it solve? Setting up and debugging a Turborepo monorepo involves many subtle configuration decisions—task dependencies, cache outputs, environment variable hashing, and CI filtering—where small mistakes silently break caching or parallelization. This Skill provides structured guidance, decision trees, and anti-pattern detection so your turbo.json, package scripts, and CI workflows follow Turborepo best practices from the start. ## Core Features & Use Cases - Task Pipeline Configuration: Register package tasks in turbo.json with correct dependsOn (^build vs build), outputs, inputs, and persistent settings, always preferring package tasks over root tasks. - Cache Debugging & Optimization: Diagnose cache misses with --summarize and --dry, configure remote caching with TURBO_TOKEN/TURBO_TEAM, and fix missing outputs or unhashed environment variables. - Filtering & CI Setup: Run only changed packages with --affected, use --filter syntax for names, directories, and git ranges, and set up GitHub Actions or Vercel deployments with turbo-ignore. - Use Case: Your CI builds every package on every pull request. Use this Skill to switch to turbo run build test lint --affected with proper fetch-depth and remote caching, so only changed packages and their dependents are rebuilt. ## Quick Start Ask the assistant to review your turbo.json and package.json scripts and configure a build, lint, and test pipeline that caches outputs and runs only affected packages in CI.
