turborepo

Coordinate task execution across a monorepo with Turborepo.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mend-detection-qa/turborepo --skill turborepo-mend-detection-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/mend-detection-qa/turborepo/tree/main/skills/turborepo
Command: npx skills add https://github.com/mend-detection-qa/turborepo --skill turborepo-mend-detection-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and optimizes task execution across a monorepo by orchestrating dependencies, caching, and parallelization with Turborepo.

Core Features & Use Cases

  • Per-package tasks and package configurations enable parallel execution and independent caching across apps and packages
  • Efficient CI and developer workflows using --affected and --filter to run only changed work
  • Package-level configuration and root turbo.json layering promote scalable, maintainable monorepos

Quick Start

Define per-package scripts in each package, then register tasks in root turbo.json and run turbo run <task> to execute.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I optimize monorepo task execution with caching and parallelization?

You can optimize monorepo task execution by orchestrating dependencies, caching, and parallelization with Turborepo. Define per-package scripts in each package, register tasks in the root turbo.json, and execute them using the turbo run command.

How do I configure per-package tasks in a monorepo build system?

To configure per-package tasks in a monorepo build system, define individual scripts within each package and then register those tasks in the root turbo.json file. This approach enables independent caching and parallel execution across apps and packages.

Can I run selective builds for only changed packages in a CI workflow?

Yes, you can run selective builds for changed packages in a CI workflow by using the --affected and --filter flags. This executes only the work that has changed, creating efficient CI and developer workflows.

What is the best way to layer root and package configurations in a monorepo?

The best way to layer configurations is to use root turbo.json layering alongside package-level configuration. Following this best practice ensures scalable, maintainable monorepos with correctly defined outputs and dependsOn syntax.

Why do I need to define outputs and dependsOn syntax for monorepo tasks?

Defining outputs and dependsOn syntax is required to ensure correct task orchestration and caching across your monorepo. Proper configuration allows the build system to track dependencies accurately and cache task results effectively.