turborepo

Configure Turborepo tasks, pipelines, caching, and filtering across monorepo packages.

12|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/beeman/solana-mobile-monorepo --skill turborepo-beeman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turborepo
Source: https://github.com/beeman/solana-mobile-monorepo/tree/main/.ruler/skills/turborepo
Command: npx skills add https://github.com/beeman/solana-mobile-monorepo --skill turborepo-beeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams orchestrate Turborepo monorepo workflows, enabling scalable task graphs and efficient caching.

Core Features & Use Cases

  • Package-level tasks: declare per-package tasks that Turborepo can parallelize and cache.
  • Workflow pipelines: define dependencies, outputs, and filters to drive CI and local development.
  • Best-practice guidance: explains root vs package configs, and how to structure turbo.json for scalable repos, with examples for apps and packages.

Quick Start

Start by wiring a root turbo.json and per-package turbo.json overrides. Use turbo run to orchestrate build, lint, and test across packages. Add package scripts and leverage filtering to run in specific scopes.

Frequently Asked Questions about turborepo

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

FAQPage Schema
How do I configure task pipelines in a monorepo using turbo.json?

You define workflow pipelines in a root turbo.json by specifying task dependencies, outputs, and filters, which allows Turborepo to orchestrate builds, lint, and tests across monorepo packages.

How does monorepo caching work for CI and local development?

Monorepo caching works by storing task outputs in turbo.json, allowing CI and local development to skip redundant computations, restore cached results, and parallelize package-scoped tasks efficiently.

What is the difference between root and package-level turbo.json configurations?

Root turbo.json configurations define global task pipelines and caching rules, while package-level overrides allow specific apps or packages to customize task behavior within the monorepo workflow.

How do I run tasks for specific packages with monorepo filtering?

You apply monorepo filtering by passing scope arguments to turbo run, restricting task orchestration to specific packages or directories, ensuring targeted builds, lint, and test executions across apps.

Can I integrate Turborepo task orchestration into existing CI pipelines?

Yes, you can integrate Turborepo into CI pipelines by wiring a root turbo.json, using turbo run to orchestrate tasks, and leveraging caching and filtering to optimize monorepo workflow execution.

When should I use package-level task overrides instead of root configurations?

Use package-level turbo.json overrides when specific apps or packages require custom task dependencies or outputs, whereas root configurations establish the baseline monorepo workflow pipelines and caching rules.