turborepo

Configure per-package tasks and caching for Turborepo monorepo workflows.

Updated Mar 1, 2026

Search Tags:#workflow #caching #monorepo #turborepo #ci #package-config

Ready to run

npx skills add https://github.com/RyanCallahan312/crayon --skill turborepo-ryancallahan312

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/RyanCallahan312/crayon/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/RyanCallahan312/crayon --skill turborepo-ryancallahan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo centralizes and speeds tasks across a monorepo by enabling per-package tasks, dependency-aware caching, and efficient pipelines, reducing build times and enabling scalable workflows.

Core Features & Use Cases

Package-scoped tasks run in parallel across apps and packages
Dependency-aware caching and selective rebuilds for CI and local development
Package Configurations to tailor turbo.json per package and enable per-package overrides
Flexible filtering patterns like --affected to target changed packages and dependents
Remote caching integration for fast, repeats across environments
Real-world example: validate an entire monorepo when merging PRs or run focused checks for a single package and its deps

Quick Start

Create per-package turbo.json configurations and delegate tasks to turbo run commands to orchestrate builds across the monorepo.

Frequently Asked Questions about turborepo

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

FAQPage Schema

How do I configure per-package tasks to run in parallel across a monorepo?▼

Per-package tasks are configured using package-level turbo.json files that define task definitions, enabling Turborepo to run monorepo builds and tests in parallel while caching outputs for faster CI workflows.

What is dependency-aware caching and how does it speed up monorepo builds?▼

Dependency-aware caching stores build outputs based on task inputs and dependencies, allowing Turborepo to skip redundant work and selectively rebuild only affected packages during local development and CI pipelines.

Can I use filtering patterns to target only changed packages in a CI pipeline?▼

Yes, Turborepo supports flexible filtering patterns like --affected to target changed packages and their dependents, optimizing CI by running focused checks instead of validating the entire monorepo on every change.

How do I handle environment variables and global options in a Turborepo setup?▼

Turborepo handles environment variables and global options through root and package configurations, allowing you to declare env dependencies in turbo.json so cached outputs invalidate correctly when environment values change.

What's the best way to structure task dependencies for multi-package builds?▼

The best approach is defining task dependencies in turbo.json so Turborepo understands the correct execution order, ensuring package-scoped builds respect cross-package dependencies and run efficiently in parallel where possible.

Does Turborepo support remote caching for repeated builds across different environments?▼

Yes, Turborepo supports remote caching integration that stores build outputs externally, enabling fast repeat builds across local development and CI environments by retrieving cached results instead of re-running tasks.