batch-orchestration
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
Profile →npx skills add rohitg00/pro-workflow --skill batch-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Batch Orchestration The `/batch` command pattern for large-scale parallel changes. ## How It Works ```text /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 `
What does the batch-orchestration skill do?
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
How do I install it?
Run `npx skills add rohitg00/pro-workflow --skill batch-orchestration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/pro-workflow, a repository with 2,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.