Skip to content
BENIBIX Learn

/batch Command

Also known as /batch, Parallel change, Large-scale change

It splits a big change into parts that run side by side.

Think of it like

It is like a big puzzle. Many friends each do one corner at the same time.

Example

Jack must rename a logging call in 200 files. /batch splits the folders into 12 parts, and an hour later he has 12 small pull requests to review.

Why it matters

A change too big for one session gets done all at once, in small parts a person can check.

Definition

/batch is a bundled skill for one large change across a codebase. It reads the code, splits the work into 5 to 30 parts that do not depend on each other, and shows you the plan. Once you approve it, it starts one background subagent per part, each in its own worktree. Each helper makes its change, runs the tests and opens a pull request or says what went wrong. It needs a git repository.

Example code

console
/batch migrate src/ from JavaScript to TypeScript
Plan a big change and run its parts side by side.
One plan becomes many parts. Each part gets its own helper, worktree and pull request.

Common mistake

Using it for steps that depend on each other. Each part runs alone, so a part that needs another one's result will fail.

Key takeaways

  1. 1
    Plan first. You approve it.
  2. 2
    5 to 30 parts. Each on its own.
  3. 3
    One worktree each. One pull request each.

Learn it properly