Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/batch-orchestration
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees.
Passed 20 of 22 test cases with the skill, and 8 of 22 without it.
and 9 more in the full report
12 fixed8 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What artifact must each successful background agent produce at the end of its worktree execution before the collection phase?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that each agent runs tests and opens a pull request. | Missed | Passed |
The instructions your model reads when the skill loads.
The /batch command pattern for large-scale parallel changes.
/batch <instruction>
│
├── 1. Research: scan repo, understand scope
├── 2. Decompose: split into 5-30 independent units
├── 3. Present plan: show units, ask for approval
├── 4. Execute: one background agent per unit in isolated worktree
└── 5. Collect: each agent runs tests and opens a PR
/batch Convert all React class components to function components
/batch Add error boundaries to every page component
/batch Migrate from moment.js to dayjs across the codebase
/batch Add OpenTelemetry tracing to all API handlers
The instruction should describe the change pattern, not individual files. The batch system finds the files.
The orchestrator scans the repo to find every instance that matches the instruction:
grep -r "class.*extends.*Component" --include="*.tsx" -l
It builds a complete list of targets and groups them by independence.
Each unit must be:
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.