turborepo

Configure per-package tasks and root turbo.json for monorepo orchestration.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Lschulzes/meal-planning --skill turborepo-lschulzes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/Lschulzes/meal-planning/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/Lschulzes/meal-planning --skill turborepo-lschulzes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo monorepo guidance for building, caching, and orchestrating tasks across multiple apps and packages, enabling scalable and parallel workflows.

Core Features & Use Cases

  • Per-package tasks: define build, lint, test for each package that can run in parallel.
  • Package configurations: customize outputs and env for specific packages while keeping a clean root config.
  • CI optimization: leverage --affected, filters, and remote caching to speed up pipelines in PRs and main branch builds.

Quick Start

Configure your workspace with per-package scripts and root turbo.json, then run turbo run build to validate parallel execution and caching.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I orchestrate monorepo pipelines with parallel task execution?

To configure monorepo caching, apply safe patterns for package configurations and global options in your root turbo.json to ensure correct cache key calculation and enable parallel execution across packages.

How do I speed up CI pipelines for a multi-package monorepo?

Speed up monorepo CI pipelines by leveraging --affected filters, scoped package filtering, and remote caching to reduce build times and avoid running unnecessary tasks during pull requests and main branch builds.

When do I need to configure per-package tasks in a monorepo?

You need per-package tasks when working in a multi-package project with separate apps and libraries, allowing you to define distinct build, lint, and test scripts that can run in parallel.

How do I customize build outputs and environment variables for specific packages?

Customize package configurations to define specific outputs and environment variables for individual packages while maintaining a clean root turbo.json configuration for global monorepo options.

What is the best way to structure a root configuration for monorepo task orchestration?

The best way to structure monorepo task orchestration is to enforce safe patterns in a clean root turbo.json, delegating specific outputs and environments to individual package-level configurations.

Why are my monorepo cache keys calculating incorrectly during parallel builds?

Incorrect cache key calculation in monorepo builds often occurs when safe patterns for package configurations and global options are not properly enforced within the root turbo.json configuration.