turborepo

Orchestrate Turborepo monorepos with dependency-aware task execution and caching.

5.7k|318|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/antfu/skills --skill turborepo-antfu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/antfu/skills/tree/main/skills/turborepo
Command: npx skills add https://github.com/antfu/skills --skill turborepo-antfu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo orchestration simplifies managing multi-package builds by providing a centralized way to run and cache tasks across packages, delivering faster and more reproducible builds.

Core Features & Use Cases

  • Dependency-aware task execution across packages with parallelization and incremental caching.
  • Per-package configuration via root and package turbo.json files, including package-specific outputs, inputs, env, and transit patterns.
  • CI optimization using --affected, advanced filtering, and remote caching to speed up pipelines.

Quick Start

Initialize a root turbo.json, add per-package turbo.json configurations, and start with turbo run build --affected to validate changes.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I speed up monorepo builds with caching?

Monorepo builds are accelerated by orchestrating dependency-aware task execution with incremental caching, allowing parallel packages to skip redundant work and deliver faster, reproducible results.

How do I configure per-package tasks in a Turborepo monorepo?

Per-package tasks in a Turborepo monorepo are configured using root and package turbo.json files, which specify package-specific outputs, inputs, environment variables, and transit patterns for scalable builds.

What is the best way to run only affected packages in CI?

Running only affected packages in CI is achieved using the --affected flag with advanced filtering, which limits task execution to changed packages and utilizes remote caching to speed up pipelines.

How does dependency-aware task execution work across multiple packages?

Dependency-aware task execution works by orchestrating tasks across multiple packages in parallel, respecting inter-package dependencies to ensure correct build order while leveraging incremental caching.

When do I need a turbo.json file for my monorepo workflow?

You need a turbo.json file to enforce correct centralized configuration for scalable monorepo workflows, defining task inputs, outputs, and environment variables for consistent cached execution across packages.

Why are my Turborepo cached tasks not reproducing correctly?

Cached tasks may not reproduce correctly if turbo.json configurations lack proper inputs, outputs, or environment variable definitions, breaking dependency-aware execution and causing inconsistent monorepo builds.