turbo

Diagnoses and fixes Turbo configuration errors inTurborepo workspaces, including schema migrations from pipeline to tasks.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/morgs32/skills --skill turbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turbo
Source: https://github.com/morgs32/skills/tree/main/skills/turbo
Command: npx skills add https://github.com/morgs32/skills --skill turbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix and update Turborepo (Turbo) configuration and task setup. Use for turbo.json errors, schema updates (pipeline -> tasks), and package-level config issues like missing extends.

Core Features & Use Cases

  • Identify whether the error references root or package config.
  • If a package-level turbo.json exists, ensure it includes extends: ["//"] to inherit the root configuration.
  • Update deprecated keys: rename pipeline to tasks for Turbo 2+ configs.

Quick Start

Run the turbo skill to fix a package-level turbo.json by adding extends: ["//"] if missing and migrate "pipeline" keys to "tasks".

Frequently Asked Questions about turbo

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

FAQPage Schema
How do I migrate Turborepo pipeline to tasks configuration?

To migrate Turborepo configs, rename deprecated pipeline keys to tasks for Turbo 2+ standards. This updates your turbo.json schema to align with current Turborepo task configuration requirements.

Why does my package-level turbo.json not inherit root config?

Package-level turbo.json files require an extends entry pointing to the root. Add extends: ["//"] to inherit root configuration and ensure workspace settings cascade correctly.

What causes turbo.json schema errors in a monorepo?

Turbo.json schema errors often stem from deprecated pipeline keys or missing extends entries in package configs. Diagnosing whether the error references root or package config identifies the specific issue.

How do I fix Turborepo configuration errors across packages?

Fix Turborepo errors by identifying if the issue is root or package-level, adding extends: ["//"] to package configs, and migrating deprecated pipeline keys to tasks for Turbo 2+ compatibility.

Do I need extends in every package turbo.json?

Yes, package-level turbo.json files should include extends: ["//"] to inherit the root configuration. This ensures all packages share base workspace settings and task definitions.

Can I use deprecated pipeline keys with Turbo 2+?

Pipeline keys are deprecated in Turbo 2+ and must be migrated to tasks. The turbo configuration update renames pipeline entries to tasks to align with current Turborepo standards.