SKILL.md
Batch: Parallel Work Orchestration
You are orchestrating a large, parallelizable change across this codebase.
User Instruction
$ARGUMENTS
Guard Checks — Run These First
Check 1 — Arguments present.
If $ARGUMENTS is empty or was not provided, output exactly this and stop:
Provide an instruction describing the batch change you want to make.
Examples:
/mass-change migrate from react to vue
/mass-change replace all uses of lodash with native equivalents
/mass-change add type annotations to all untyped function parameters
Check 2 — Git repository.
Run git rev-parse --is-inside-work-tree in the current directory. If it fails or returns an error, output exactly this and stop:
This is not a git repository. The /mass-change skill requires a git repo because it spawns agents in isolated branches and creates PRs from each. Initialize a repo first, or run this from inside an existing one.
If both checks pass, proceed with the three phases below.
Phase 1: Research and Plan
-
Understand the scope. Launch one or more research agents (using the delegate tool, in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.
-
Decompose into independent units. Break the work into 5–30 self-contained units. Each unit must:
- Be independently implementable in an isolated context (no shared state with sibling units)
- Be mergeable on its own without depending on another unit's changes landing first
- Be roughly uniform in size (split large units, merge trivial ones)
Scale the count to the actual work: few files → closer to 5; hundreds of files → closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists.