turborepo

Configure Turborepo turbo.json tasks with dependsOn, outputs, inputs, and env for caching.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/dunlo --skill turborepo-frekimanagarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/FrekiManagarm/dunlo/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/FrekiManagarm/dunlo --skill turborepo-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turborepo Skill reduces slow, wasteful monorepo workflows by helping you correctly configure task orchestration, caching, and CI execution so builds run only when needed and in the right order.

Core Features & Use Cases

  • Task orchestration for monorepos: Configure turbo.json tasks using dependsOn and package task patterns to enable parallel execution across packages.
  • Correct caching behavior: Define outputs, inputs, and env so cache hits are valid and cache misses are explainable, including strategies for debugging with --summarize and --dry.
  • CI and targeted execution: Use --affected and --filter to run only changed packages (and dependents) in CI while keeping environment handling consistent.

Quick Start

Ask to set up or fix a Turborepo turbo.json so that build, lint, and test tasks run in the correct dependency order with proper outputs, cache inputs, and CI-friendly --affected usage for a monorepo that uses multiple apps/ and packages/.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I configure turborepo task orchestration to run builds in the correct dependency order?

Configure turborepo task orchestration by defining tasks in turbo.json with dependsOn and package task patterns to enable parallel execution across packages. This ensures build, lint, and test tasks run in the correct dependency order with proper outputs and cache inputs.

Why are my turborepo cache misses happening unexpectedly during CI builds?

Turborepo cache misses occur when outputs, inputs, and environment variable hashing are misconfigured in turbo.json. Define precise env settings and inputs to ensure cache hits are valid and cache misses are explainable, debugging with --summarize and --dry.

How do I run only changed packages in a monorepo CI pipeline?

Run only changed packages in a monorepo CI pipeline by using the --affected and --filter flags with turborepo. This executes targeted tasks for changed packages and their dependents while keeping environment handling consistent across your apps and packages.

What are common anti-patterns when setting up turbo.json for a monorepo?

Common turbo.json anti-patterns include placing task logic at the root level instead of package-level scripts, incorrect turbo command usage, and imprecise dependsOn, outputs, or env settings. Guard against these to ensure deterministic cached results and eliminate redundant work.

Can I use turborepo caching with multiple apps and shared packages in a monorepo?

Turborepo caching supports monorepos with multiple apps and packages by configuring package-level scripts in turbo.json. Correctly define task outputs, cache inputs, and environment variables to eliminate redundant work and ensure deterministic cached results across all packages.