turborepo

Orchestrate build tasks across a monorepo with caching and parallel execution.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/Monosen/golink --skill turborepo-monosen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/Monosen/golink/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/Monosen/golink --skill turborepo-monosen

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Turborepo provides a single, scalable solution to orchestrate tasks across a multi-package repository, enabling caching and parallel execution to significantly speed up builds.

## Core Features & Use Cases

  • Per-package task scripts to enable parallel builds across apps and libraries
  • Global and package-specific configuration with turbo.json
  • Efficient caching with inputs/outputs, --affected filters, and package-specific configurations
  • CI/PR validation and monorepo refactors

### Quick Start Create a root turbo.json and run turbo run build to validate the workflow.

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 tasks across packages with parallel execution and caching. Using a turbo.json configuration, you define pipelines that cache inputs and outputs, skipping redundant work and delivering consistent, scalable builds.

How do I run per-package tasks in parallel across a multi-package repository?

Per-package tasks are executed in parallel by configuring task scripts within a root or package-specific turbo.json. This orchestration applies pipeline configurations to apps and libraries, handling environment variables and inputs to optimize execution.

What is the best way to validate CI and PR changes in a monorepo?

CI and PR validation in a monorepo is handled using --affected filters to run tasks only on changed packages. This applies pipeline configurations and caching to ensure consistent builds without processing unaffected code.

Can I configure package-specific tasks and caching rules in a monorepo?

Package-specific tasks and caching rules are configured using turbo.json files at the root or package level. This enables customized task inputs, outputs, and environment variable handling for individual apps and libraries within the monorepo.

Do I need a root turbo.json to orchestrate monorepo tasks?

A root turbo.json is needed to define global pipeline configurations and orchestrate monorepo tasks. While package-specific configurations are supported, the root file establishes the baseline for caching, inputs, and parallel execution across the repository.