turborepo

Orchestrate monorepo tasks with turbo.json caching and parallel execution.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Situ2000/skills-main --skill turborepo-situ2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/Situ2000/skills-main/tree/main/skills/turborepo
Command: npx skills add https://github.com/Situ2000/skills-main --skill turborepo-situ2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo provides a centralized workflow for coordinating and speeding up builds, tests, and other tasks across a multi-package repository by caching results and orchestrating parallel execution.

Core Features & Use Cases

  • Task graph orchestration with dependsOn, per-package turbo.json overrides, and transit nodes for parallelism
  • Local and remote caching to accelerate CI and development across packages
  • Fine-grained env and inputs handling with global and per-task configuration for deterministic builds
  • Package configurations enabling framework-specific outputs and isolated package rules

Quick Start

Configure per-package turbo.json files and run turbo run build --affected to start.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I speed up builds and tests across a multi-package repository?

Monorepo build orchestration speeds up multi-package tasks by caching results and orchestrating parallel execution. It coordinates builds and tests across packages to reduce CI times and accelerate development.

What is the best way to configure task dependencies in a monorepo?

Task graph orchestration uses dependsOn rules and transit nodes to define task dependencies. Per-package turbo.json overrides allow isolated package rules, enabling parallel execution and incremental builds across the repository.

How do I set up local and remote caching for incremental builds?

Caching rules define inputs and outputs to enable local and remote caching for incremental builds. Fine-grained environment handling with global and per-task configurations ensures deterministic builds and accelerates CI pipelines.

Can I apply framework-specific configurations to individual packages in a monorepo?

Package configurations support framework-specific outputs and isolated package rules via per-package turbo.json overrides. This allows individual packages within the shared code repository to define their own task behaviors.

How do I run only the tasks affected by recent changes in a monorepo?

Running turbo run build with the affected flag executes only tasks impacted by recent changes. This leverages the task graph and caching rules to skip unaffected packages, optimizing execution time.