turborepo

Turborepo monorepo build system and orchestration. Covers task pipelines, dependsOn syntax, caching configuration, remote cache, filtering, CI optimization, environment variables, workspace management, watch mode, package boundaries, and code generation. Use when configuring tasks, creating packages, setting up monorepo, sharing code between apps, running changed packages, debugging cache, optimizing CI, resolving workspace dependencies, enforcing package boundaries, or generating code.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "turborepo" with this command: npx skills add oakoss/agent-skills/oakoss-agent-skills-turborepo

Turborepo

Overview

Build system for JavaScript/TypeScript monorepos. Caches task outputs and runs tasks in parallel based on dependency graph. Always create package tasks (not root tasks), use turbo run in scripts, and let dependsOn manage execution order. Configuration uses turbo.json (or turbo.jsonc for comments).

When to use: Monorepo task orchestration, build caching, CI optimization, workspace dependency management, package boundary enforcement.

When NOT to use: Single-package projects, non-JavaScript monorepos, projects without build steps.

Quick Reference

PatternSyntaxKey Points
Schema"$schema": "https://turborepo.dev/schema.json"Always include in turbo.json
Dependency build"dependsOn": ["^build"]Build dependencies first
Same-package task"dependsOn": ["codegen"]Run in same package first
Specific package"dependsOn": ["pkg#task"]Named package's task
Parallel lint/typecheckTransit Nodes patternCache invalidation without sequential execution
Dev server"persistent": true, "cache": falseLong-running, non-cacheable
Sidecar tasks"with": ["api#dev"]Run tasks concurrently alongside
Watch modeturbo watch devRe-run on file changes
Filter by package--filter=webSingle package
Filter with deps--filter=web...Package + dependencies
Changed packages--affectedChanged + dependents
Debug cache--summarize or --drySee hash inputs
Package configturbo.json with "extends": ["//"]Per-package overrides
Composable config"extends": ["@repo/config"]Extend from any workspace package
Extend arrays"$TURBO_EXTENDS$" in arraysAppend to inherited config instead of replacing
Env vars in hash"env": ["API_URL"]Cache invalidation on change
Boundariesturbo boundariesEnforce package isolation and import rules
Query graphturbo queryGraphQL interface to package/task graphs
Code generationturbo generateScaffold new packages and components
List packagesturbo lsList all packages in monorepo
Devtoolsturbo devtoolsVisual Package Graph and Task Graph explorer
Docker pruned workspaceturbo prune <pkg> --dockerMinimal monorepo slice for container builds

Decision Trees

Configure a Task

Configure a task?
+-- Define task dependencies       -> dependsOn in turbo.json
+-- Lint/check-types (parallel)    -> Transit Nodes pattern
+-- Specify build outputs          -> outputs key
+-- Handle environment variables   -> env key or globalEnv
+-- Dev/watch tasks                -> persistent: true, cache: false
+-- Sidecar tasks (run alongside)  -> with key
+-- Package-specific config        -> Package turbo.json with extends: ["//"]
+-- Composable config              -> extends from any workspace package
+-- Global settings                -> globalEnv, globalDependencies, cacheDir

Cache Problems

Cache problems?
+-- Outputs not restored           -> Missing outputs key
+-- Unexpected cache misses        -> Use --summarize or --dry to debug
+-- Skip cache entirely            -> --force or cache: false
+-- Remote cache not working       -> Check turbo login/link
+-- Environment causing misses     -> Var not in env key

Filter Packages

Filter packages?
+-- By package name                -> --filter=web
+-- By directory                   -> --filter=./apps/*
+-- Package + dependencies         -> --filter=web...
+-- Package + dependents           -> --filter=...web
+-- Changed + dependents           -> --affected

Explore Repository

Explore repository?
+-- List all packages              -> turbo ls
+-- Query dependency graph         -> turbo query
+-- Visualize graphs               -> turbo devtools
+-- Check boundary violations      -> turbo boundaries
+-- Generate new package           -> turbo generate workspace
+-- Run custom generator           -> turbo generate run [name]

Common Mistakes

MistakeCorrect Pattern
Putting build logic in root package.json scripts instead of per-packageDefine scripts in each package and use turbo run in root to delegate
Using ^build without declaring workspace:* dependencyAdd the dependency in package.json first; ^build only triggers for declared dependencies
Chaining turbo tasks with && in package scriptsUse dependsOn in turbo.json to declare task ordering
Not adding environment variables to the env key in turbo.jsonDeclare all build-affecting env vars in env so cache hashes correctly
Using --parallel flag to bypass dependency orderingConfigure dependsOn correctly or use transit nodes for parallel tasks with proper cache invalidation
Using outdated schema URLUse https://turborepo.dev/schema.json in $schema field
Overriding inherited arrays in package configsUse $TURBO_EXTENDS$ in arrays to append instead of replace
Defining tasks in root turbo.json that belong to a specific packageDefine tasks inside the package's own turbo.json with extends: ["//"]
Using turbo <task> shorthand in scripts or CIUse turbo run <task> in package.json scripts and CI pipelines; shorthand is for interactive use only

Delegation

  • Monorepo structure exploration: Use Explore agent to discover packages, workspace layout, and dependency relationships
  • Pipeline configuration and optimization: Use Task agent to set up turbo.json tasks, configure caching, and debug cache misses
  • Monorepo architecture planning: Use Plan agent to design package boundaries, shared libraries, and CI optimization strategy

If the pnpm-workspace skill is available, delegate workspace setup, dependency linking, catalogs, and pnpm deploy to it. If the changesets skill is available, delegate versioning, changelog generation, and npm publishing to it.

References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

github-cli

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

tanstack-cli

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

typescript-patterns

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

tanstack-devtools

No summary provided by upstream source.

Repository SourceNeeds Review