turborepo

Orchestrate monorepo tasks with caching and dependency graphs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo provides a structured approach to orchestrating tasks across a monorepo, enabling parallel execution, caching, and scalable pipelines to speed up development and CI.

Core Features & Use Cases

  • Package-scoped tasks: run per-package scripts in parallel to accelerate feedback.
  • Caching & dependency graph: reuse outputs and only recompute changed packages.
  • Use Case: manage builds for apps and libraries, run affected tests in PRs, and optimize CI pipelines.

Quick Start

Install Turborepo in your repo, define a turbo.json with per-package tasks, and run turbo run build to validate a full build locally or in CI.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I automate monorepo task orchestration to speed up builds?

Automate monorepo task orchestration by defining a turbo.json with per-package tasks and running turbo run build. This enables parallel execution and caching across multi-package projects to accelerate builds and CI pipelines.

How does caching work for monorepo task execution?

Caching in monorepo task execution works by defining inputs and outputs caching rules in turbo.json. It reuses previous outputs and only recomputes tasks for changed packages using a dependency graph, skipping redundant work during local development and CI.

How do I enforce task dependencies in a multi-package project?

Enforce task dependencies in a multi-package project using the dependsOn syntax within turbo.json configurations. This ensures structured task orchestration across apps and packages, validating that prerequisite builds or tests complete before downstream tasks run.

Can I run affected tests in PR validation for a monorepo?

You can run affected tests in PR validation for a monorepo by applying package-scoped tasks. This approach runs per-package scripts in parallel and leverages caching to only test packages impacted by the changes, optimizing CI pipelines.

What is the best way to scale CI pipelines for apps and libraries?

The best way to scale CI pipelines for apps and libraries is implementing structured task orchestration with caching. Defining per-package turbo.json configurations allows parallel execution and output reuse, preventing pipeline bottlenecks in large projects.

Do I need per-package turbo.json configurations for local development workflows?

Per-package turbo.json configurations are needed to manage local development workflows effectively. They allow you to define specific inputs, outputs caching rules, and dependsOn syntax for individual packages, ensuring correct parallel execution and feedback acceleration.