- name
- batch_migration_orchestrator
- description
- Use when the user wants a large, mechanical change split into many independent units and executed in parallel with isolated workers and PRs.
Batch Migration Orchestrator
Use this skill for sweeping refactors, migrations, bulk renames, or repetitive codebase-wide edits.
Goal
Turn one large request into a safe parallel rollout with independent units, validation, and mergeable outputs.
Workflow
- Inspect the repo to find every affected area, convention, and dependency.
- Split the change into independent units by module, directory, or subsystem.
- Define an end-to-end verification recipe for each unit.
- Launch workers in parallel only when their write scopes do not overlap.
- Track completion, collect PRs or patches, and summarize failures.
Guardrails
- Do not parallelize tightly coupled work.
- Do not let workers edit the same files.
- Require each worker to validate its own unit.
- Prefer worktree or isolated branch execution when git is available.
Inputs
- Migration target
- Scope boundaries
- Verification method
- Branch/PR expectations
Source Provenance
Derived from Claude Code bundled skill logic in src/skills/bundled/batch.ts.