turborepo

Configure turbo.json tasks and caching for monorepo builds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo guidance for configuring monorepos, orchestrating tasks, caching, and CI optimization to speed up builds and maintain consistency across apps and packages.

Core Features & Use Cases

  • Package-scoped task definitions with per-package turbo.json
  • Advanced caching strategies including remote caching and hash inputs
  • CI optimization patterns and filter-based selection for PRs
  • Boundaries and monorepo structure best practices for scalable repos

Quick Start

Create per-package turbo.json and minimal root turbo.json, then run turbo run across packages to execute tasks.

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 and CI optimization?

Speed up monorepo builds by configuring centralized task orchestration and caching. Define package tasks and explicit outputs to ensure correct cache behavior and predictable builds across apps and packages.

What is the best way to configure turbo.json for a monorepo workspace?

Configure turbo.json by creating a minimal root file and per-package configurations. This structure defines task execution, enforces boundaries, and handles environment variables to ensure correct caching across the workspace.

How does remote caching work for CI pipelines in a monorepo?

Remote caching stores build outputs keyed by hash inputs, allowing CI pipelines to skip redundant tasks. Filter-based selection runs only affected packages, accelerating CI pipelines across the monorepo.

Can I run tasks for specific packages during a pull request?

Yes, you can run tasks for specific packages using filter-based selection. This CI optimization pattern targets only affected apps and packages during a pull request, reducing execution time.

Why does my monorepo task fail due to incorrect cache behavior?

Monorepo tasks fail when package boundaries or environment handling are misconfigured. Enforce per-package boundaries and define explicit outputs in turbo.json to ensure correct cache behavior and predictable builds.

When do I need to define explicit outputs for monorepo package tasks?

Define explicit outputs when configuring package tasks to ensure correct cache behavior. Explicit outputs tell the task graph what files to cache, ensuring predictable builds and preventing stale cache hits across apps.