turborepo

Configure Turborepo task pipelines and caching rules for monorepo builds.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/junwen-k/cookie-store --skill turborepo-junwen-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/junwen-k/cookie-store/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/junwen-k/cookie-store --skill turborepo-junwen-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo provides a centralized way to orchestrate tasks across a multi-package repository, reducing build times and complexity by reusing cache and parallelizing work.

Core Features & Use Cases

  • Dependency-aware task graph with per-package and root tasks
  • Per-package caching and parallel execution for apps and libraries
  • Use cases include CI optimization, monorepo management, and incremental builds

Quick Start

  • Define package-level tasks in each package's package.json
  • Register tasks in the root turbo.json
  • Run turbo run build --affected to validate changes and caching

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I optimize multi-package builds and reduce build times in a monorepo?

Multi-package builds in a monorepo are optimized by using task orchestration to parallelize work and reuse cached outputs. This approach reduces build times and complexity by executing dependency-aware pipelines across apps and packages.

How do I configure per-package tasks and root pipelines using turbo.json?

Per-package tasks are defined in each package's package.json, then registered and configured in the root turbo.json. You apply caching rules using dependsOn, inputs, outputs, and env keys to orchestrate the overall build pipeline.

What is the best way to set up CI optimization for incremental builds in a monorepo?

CI optimization for incremental builds is achieved by running affected tasks via a dependency-aware task graph. This validates changes and reuses cached outputs, ensuring only necessary work is executed across the repository.

Can I execute root tasks separately from package configurations in a monorepo?

Root tasks and per-package tasks are both supported in monorepo configurations. A centralized task graph orchestrates these tasks across apps and libraries, allowing distinct root pipelines and package-level caching rules to coexist.

How does caching work for task orchestration across apps and libraries?

Caching for task orchestration works by matching configured inputs, outputs, and environment variables. When tasks are executed, the system checks the cache to reuse previous outputs, preventing redundant work across apps and libraries.