turborepo

Coordinate and optimize build workflows across a monorepo with caching and parallelization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo coordinates and optimizes build workflows across a multi-package repository, dramatically reducing build times and coordination overhead.

Core Features & Use Cases

  • Dependency-aware task orchestration across apps and packages
  • Per-package configuration via turbo.json and package configurations
  • Efficient CI by using --affected, filters, and caching to validate changes

Quick Start

Execute a turbo run across the monorepo to build, test, and verify changes with caching and parallel execution.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I speed up builds in a monorepo using caching and parallelization?

To speed up monorepo builds, coordinate dependency-aware task orchestration across apps and packages, enabling caching and parallel execution to dramatically reduce build times and coordination overhead.

How do I configure build pipelines and env handling in turbo.json?

Configure build pipelines and env handling in turbo.json by defining per-package tasks and environment variables, satisfying the configuration requirements to coordinate workflows across multi-package projects.

What is the best way to run only affected packages in CI pipelines?

The best way to run affected packages in CI pipelines is using filters and the --affected flag, applying caching to validate changes precisely and efficiently across the monorepo task graph.

How does dependency-aware task orchestration work across multi-package projects?

Dependency-aware task orchestration works by mapping the task graph across apps and packages, executing build workflows in parallel while respecting dependency order to optimize complex CI pipelines.

Can I use this to optimize complex task graphs for multi-package projects?

Yes, you can optimize complex task graphs for multi-package projects by applying precise filtering, caching, and parallelization to coordinate build workflows and reduce overall CI validation time.