turborepo-monorepo

Configures Turborepo task graphs, caching, and workspace scripts for monorepo builds.

Updated Aug 8, 2026
One-click install
npx skills add https://github.com/wolfstar-project/code-zero --skill turborepo-monorepo-wolfstar-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: turborepo-monorepo
Source: https://github.com/wolfstar-project/code-zero/tree/main/.skills/turborepo-monorepo
Command: npx skills add https://github.com/wolfstar-project/code-zero --skill turborepo-monorepo-wolfstar-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Monorepo builds become slow and unreliable when task graphs, cache outputs, and CI orchestration are misconfigured. This Skill guides correct changes to turbo.json tasks, workspace scripts, and caching so builds stay fast and correct. ## Core Features & Use Cases - Task Graph Configuration: Defines dependsOn relationships, inputs, outputs, and environment variables in turbo.json so tasks run in the right order with correct caching. - Cache Correctness: Ensures only real outputs are declared cacheable and validates that repeated runs produce expected cache hits without masking missing outputs. - CI Orchestration: Aligns CI jobs with compatible .turbo restore keys and root scripts instead of ad-hoc sequencing. - Use Case: When adding a new package to a pnpm workspace, use this Skill to wire its build into the Turbo graph with dependsOn: ['^build'], declare its dist output, and verify caching with a dry run. ## Quick Start Ask the assistant to review your turbo.json and package.json scripts and fix the task graph so builds cache correctly in CI.

Frequently Asked Questions about turborepo-monorepo

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

FAQPage Schema
How do I configure task dependencies in turbo.json?▼

Use dependsOn in the task definition to declare ordering. Add '^build' when a task consumes build outputs from dependency packages, and plain task names for same-package ordering.

How do I fix Turborepo cache misses in CI?▼

Declare all real outputs in the task's outputs array, include config files in globalDependencies, and list environment variables that affect results. Verify with turbo run <task> --dry=json and confirm a second run hits the cache.

Should tests and lint tasks be cached in Turborepo?▼

Tests and lint normally produce no cacheable files, so declare no outputs for them. They can still be cached by Turbo based on inputs, but you should not invent output artifacts.

When should I use turbo run --force?▼

Avoid using --force to bypass caching, since it hides an incorrect task graph. Fix the underlying inputs, outputs, or dependency declarations instead of forcing re-execution.

How do I inspect the Turborepo task graph before running?▼

Run turbo run <task> --dry=json to see the planned execution graph, including tasks, dependencies, and cache status, without executing anything. This is recommended for non-trivial graph changes.