turborepo

Configure Turborepo pipelines, caching, and per-package tasks in monorepos.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/z4nr34l/agent-setup --skill turborepo-z4nr34l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/z4nr34l/agent-setup/tree/main/shared/skills/turborepo
Command: npx skills add https://github.com/z4nr34l/agent-setup --skill turborepo-z4nr34l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and guides the configuration and execution of Turborepo monorepos, reducing manual setup and misconfigurations.

Core Features & Use Cases

  • Per-package task configuration with package.json scripts and root turbo.json integration.
  • Package Configurations to tailor outputs, env, and caching per package.
  • Guidance for root vs package tasks, and best practices for parallelization and caching in CI.
  • Use cases include setting up builds, lint, tests, and dev workflows across apps and libraries.

Quick Start

Load the Turborepo skill and activate it in your workflow by calling the turborepo skill. Then request a sample turbo run such as turbo run build --affected to test selective scope changes.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I configure Turborepo task orchestration for a monorepo?

Turborepo task orchestration is configured by defining pipelines in the root turbo.json and mapping corresponding scripts in each package's package.json. This setup automates task execution across packages and manages dependencies for builds, tests, and linting.

What is the best way to set up per-package caching and outputs in a monorepo?

Per-package caching and outputs are set up by tailoring package configurations within turbo.json. You define specific outputs, environment variables, and cache settings for each package to optimize CI pipelines and development workflows.

How do I run selective tasks for affected packages in a monorepo?

Selective task execution for affected packages is run using commands like turbo run build --affected. This targets only the packages with scope changes, reducing execution time by skipping unaffected workspaces during CI and development.

Where should I place scripts when organizing root vs package tasks in Turborepo?

Root vs package tasks are organized by placing shared orchestration logic in the root turbo.json and defining specific executable scripts within individual package.json files. This separation enforces correct execution flow and allows package-scoped task overrides.

Can I customize task overrides for individual packages in a monorepo pipeline?

Individual package task overrides are customized by defining specific configurations in turbo.json and adjusting the scripts within that package's package.json. This enforces per-package tasks and ensures correct execution flow tailored to each workspace.