turborepo

Configure Turborepo task pipelines, caching, and filtering for JavaScript monorepos.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/CarlosPavajeau/light --skill turborepo-carlospavajeau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/CarlosPavajeau/light/tree/main/.claude/skills/turborepo
Command: npx skills add https://github.com/CarlosPavajeau/light --skill turborepo-carlospavajeau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 package filtering—where small mistakes silently break caching or parallelization. This Skill provides structured guidance, decision trees, and anti-pattern detection to configure turbo.json correctly the first time. ## Core Features & Use Cases - Task Pipeline Configuration: Register package tasks in turbo.json with correct dependsOn, outputs, inputs, and env keys, following the package-tasks-over-root-tasks principle. - Cache Debugging & Optimization: Diagnose cache misses, configure remote caching, and use flags like --summarize, --dry, and --force to inspect hash inputs. - Filtering & CI Setup: Run only changed packages with --affected, write --filter expressions, and set up GitHub Actions or Vercel deployments with remote cache. - Use Case: Imagine your CI runs every build and test on each pull request. Use this Skill to add --affected filtering, configure remote caching with TURBO_TOKEN, and fix missing outputs keys so unchanged packages restore instantly from cache. ## Quick Start Ask the assistant to review your turbo.json and package.json scripts and fix any Turborepo configuration issues.

Frequently Asked Questions about turborepo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a build task in turbo.json?

Add the build script to each package's package.json, then register the task in root turbo.json with dependsOn set to ["^build"] and outputs like ["dist/**"]. The root package.json should only delegate with "turbo run build".

How do I run tasks only for changed packages in Turborepo?

Use the --affected flag, for example "turbo run build --affected", which compares against the default branch and includes dependents of changed packages. Customize the base with --affected-base=origin/develop.

Why is my Turborepo cache not working?

Common causes include missing outputs keys for file-producing tasks, environment variables not declared in the env key, or .env files absent from inputs. Debug with --summarize or --dry to inspect hash inputs.

What is the difference between dependsOn ^build and build in turbo.json?

^build runs the build task in dependency packages first, while plain build runs it in the same package. Use ^build for build ordering across packages and build for same-package prerequisites like test depending on build.

Should I use turbo or turbo run in package.json scripts?

Always use "turbo run" in package.json scripts, CI workflows, and any committed code. The shorthand "turbo <task>" is intended only for one-off terminal commands typed interactively.

How do I set up Turborepo remote caching in GitHub Actions?

Add TURBO_TOKEN as a secret and TURBO_TEAM as a variable in your repository settings, then expose them as environment variables in the workflow. Use fetch-depth of at least 2 in actions/checkout so --affected can compute the merge base.