Files
agent-skills/skills/turborepo/references/cli/RULE.md
Jason Woltje f5792c40be feat: Complete fleet — 94 skills across 10+ domains
Pulled ALL skills from 15 source repositories:
- anthropics/skills: 16 (docs, design, MCP, testing)
- obra/superpowers: 14 (TDD, debugging, agents, planning)
- coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth)
- better-auth/skills: 5 (auth patterns)
- vercel-labs/agent-skills: 5 (React, design, Vercel)
- antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo)
- Plus 13 individual skills from various repos

Mosaic Stack is not limited to coding — the Orchestrator and
subagents serve coding, business, design, marketing, writing,
logistics, analysis, and more.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 16:27:42 -06:00

101 lines
2.1 KiB
Markdown

# turbo run
The primary command for executing tasks across your monorepo.
## Basic Usage
```bash
# Full form (use in CI, package.json, scripts)
turbo run <tasks>
# Shorthand (only for one-off terminal invocations)
turbo <tasks>
```
## When to Use `turbo run` vs `turbo`
**Always use `turbo run` when the command is written into code:**
- `package.json` scripts
- CI/CD workflows (GitHub Actions, etc.)
- Shell scripts
- Documentation
- Any static/committed configuration
**Only use `turbo` (shorthand) for:**
- One-off commands typed directly in terminal
- Ad-hoc invocations by humans or agents
```json
// package.json - ALWAYS use "turbo run"
{
"scripts": {
"build": "turbo run build",
"dev": "turbo run dev",
"lint": "turbo run lint",
"test": "turbo run test"
}
}
```
```yaml
# CI workflow - ALWAYS use "turbo run"
- run: turbo run build --affected
- run: turbo run test --affected
```
```bash
# Terminal one-off - shorthand OK
turbo build --filter=web
```
## Running Tasks
Tasks must be defined in `turbo.json` before running.
```bash
# Single task
turbo build
# Multiple tasks
turbo run build lint test
# See available tasks (run without arguments)
turbo run
```
## Passing Arguments to Scripts
Use `--` to pass arguments through to the underlying package scripts:
```bash
turbo run build -- --sourcemap
turbo test -- --watch
turbo lint -- --fix
```
Everything after `--` goes directly to the task's script.
## Package Selection
By default, turbo runs tasks in all packages. Use `--filter` to narrow scope:
```bash
turbo build --filter=web
turbo test --filter=./apps/*
```
See `filtering/` for complete filter syntax.
## Quick Reference
| Goal | Command |
| ------------------- | -------------------------- |
| Build everything | `turbo build` |
| Build one package | `turbo build --filter=web` |
| Multiple tasks | `turbo build lint test` |
| Pass args to script | `turbo build -- --arg` |
| Preview run | `turbo build --dry` |
| Force rebuild | `turbo build --force` |