← Back to Skills Marketplace
83
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install 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.
README (SKILL.md)
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
Example Requests
- Migrate this monorepo from Jest to Vitest in parallel.
- Split this bulk API rename into independently shippable work units.
Inputs
- Migration goal
- Affected modules or directories
- Verification expectations
- Branch or PR policy
Outputs
- Work decomposition plan
- Parallel worker prompts
- Status tracking summary
- PR or patch rollup
Success Criteria
- Every unit has a clear scope.
- No worker write conflicts exist.
- Each unit includes verification.
Non-Goals
- One-off tiny edits
- Tightly coupled refactors that must land as one patch
Source Provenance
Derived from Claude Code bundled skill logic in src/skills/bundled/batch.ts.
Usage Guidance
This skill appears to be a reasonable blueprint for splitting and running large code migrations, but it assumes the agent can read and modify the repository and create PRs/patches without documenting required tools or credentials. Before using it: (1) verify what repository access the agent will actually have (read-only vs write/push), (2) avoid granting broad credentials — use a scoped token or run on a fork/CI runner with limited rights, (3) prefer a dry-run mode where the skill only produces patches rather than pushing them, and (4) require human review/approval before any worker pushes branches or opens PRs. If you need this to run fully autonomously, require the skill to explicitly declare required binaries (git) and the exact credential mechanism it will use.
Capability Analysis
Type: OpenClaw Skill
Name: batch-migration-orchestrator
Version: 1.0.0
The batch-migration-orchestrator skill bundle is designed to manage large-scale codebase refactors by decomposing them into isolated, parallelizable units. The instructions in SKILL.md emphasize safety guardrails, such as preventing overlapping write scopes and requiring per-unit verification, and the bundle contains no evidence of malicious intent, data exfiltration, or unauthorized execution logic.
Capability Assessment
Purpose & Capability
The name/description align with the SKILL.md: it plans and parallelizes large codebase migrations. However, the workflow explicitly references inspecting the repo, creating isolated branches/worktrees, launching workers, and producing PRs/patches — capabilities that typically require git and VCS credentials, yet the skill declares no required binaries or credentials.
Instruction Scope
Instructions are concrete and limited to decomposition, verification, and parallel execution. They instruct the agent to read the repository, split units, validate each unit, and collect PRs/patches. That is in-scope for a migration orchestrator, but the instructions implicitly require repository access and the ability to push/merge (or at least produce patches) which are not documented or constrained.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. This minimizes installation risk — nothing will be downloaded or written by an install step.
Credentials
The skill may need git, network access to remotes, and tokens for creating pushes/PRs, but it declares no required environment variables or primary credential. That absence is a proportionality gap: orchestration that creates PRs normally requires credentials (SSH keys or API tokens); the skill neither requests nor documents those, so it's unclear what privileges the agent will use to perform write operations.
Persistence & Privilege
always:false (good). Model invocation is allowed (default), meaning the agent can run this skill autonomously; combined with the environment/credential gap, that raises the blast radius if the agent has repository write permissions. The skill does not request persistent installation or modify other skills.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install batch-migration-orchestrator - After installation, invoke the skill by name or use
/batch-migration-orchestrator - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial extraction from local Claude Code source
Metadata
Frequently Asked Questions
What is Batch Migration Orchestrator?
Use when the user wants a large, mechanical change split into many independent units and executed in parallel with isolated workers and PRs. It is an AI Agent Skill for Claude Code / OpenClaw, with 83 downloads so far.
How do I install Batch Migration Orchestrator?
Run "/install batch-migration-orchestrator" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Batch Migration Orchestrator free?
Yes, Batch Migration Orchestrator is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Batch Migration Orchestrator support?
Batch Migration Orchestrator is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Batch Migration Orchestrator?
It is built and maintained by wimi321 (@wimi321); the current version is v1.0.0.
More Skills