turborepo

Automate monorepo task orchestration with Turborepo for builds, tests, and linting.

17|1|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill turborepo-deckgl-fiber-renderer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/deckgl-fiber-renderer/fiber.gl/tree/main/.agents/skills/turborepo
Command: npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill turborepo-deckgl-fiber-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turborepo provides centralized orchestration for multi-package monorepos, enabling predictable, cached task execution across packages and reducing redundant work.

Core Features & Use Cases

  • Configure per-package tasks and root tasks using turbo.json with extends
  • Leverage dependsOn, outputs, inputs, env, and package configurations for optimized builds
  • Integrate with CI patterns and boundaries to enforce package isolation and caching

Quick Start

Create a basic turbo.json in the root and per-package turbo.json overrides to begin orchestrating builds.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I configure monorepo task orchestration to parallelize builds and tests across packages?

Monorepo task orchestration automates parallelized execution, caching, and selective task runs across packages by configuring per-package tasks and root tasks using turbo.json with extends, dependsOn, outputs, inputs, and env overrides to coordinate builds, tests, and linting.

What is the best way to enforce package isolation and caching boundaries in CI workflows?

Enforcing package isolation and caching boundaries in CI workflows involves integrating centralized orchestration patterns with global options and per-package task configurations, ensuring predictable cached task execution across packages and reducing redundant work.

Can I use turbo.json overrides to coordinate selective task runs for multi-package repositories?

Yes, turbo.json overrides coordinate selective task runs for multi-package repositories by defining package-level configurations and extending root tasks, enforcing correct per-package task configuration for optimized builds, tests, and linting.

How do I set up dependsOn and outputs configurations for optimized monorepo builds?

Setting up dependsOn and outputs configurations for optimized monorepo builds requires defining per-package task configurations and global options in turbo.json, enabling parallelized execution and caching across packages to reduce redundant work in CI workflows.

When do I need centralized orchestration for a multi-package repository?

Centralized orchestration is needed for any multi-package repository requiring parallelized execution, caching, and selective task runs in CI workflows to coordinate builds, tests, and linting across packages while reducing redundant work.