batch

Orchestrate large-scale code changes across parallel git worktrees with per-unit PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/otto-assistant/bridge --skill batch-otto-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch
Source: https://github.com/otto-assistant/bridge/tree/main/cli/skills/batch
Command: npx skills add https://github.com/otto-assistant/bridge --skill batch-otto-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing large-scale code changes manually is error-prone and time-consuming, requiring coordination across many files and teams.

Core Features & Use Cases

  • Split a sweeping change into 5–30 independent work units that can be edited in parallel via isolated git worktrees.
  • Each unit yields a separate PR, enabling safer, incremental integration and easier reviews.
  • Suitable for migrations, bulk renames, and refactors that can be decomposed into self-contained tasks.

Quick Start

Plan and run a batch: outline the 5–30 work units and start parallel worktrees to implement them.

Frequently Asked Questions about batch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large code migration into parallel work units?

To split a large code migration, decompose the sweeping change into 5–30 independent work units executed in parallel across isolated git worktrees, enforcing an end-to-end plan with per-unit PRs and validation steps.

Can I run parallel refactors across multiple git worktrees?

Yes, parallel refactors are orchestrated across multiple git worktrees by isolating each work unit, enforcing an end-to-end plan, and generating reproducible per-unit PRs with explicit worker instructions and failure-handling guidance.

What is the best way to coordinate bulk code renames safely?

The best way to coordinate bulk code renames safely is splitting the change into 5–30 independent work units executed in parallel across isolated git worktrees, yielding separate PRs for incremental integration and easier reviews.

Does this batch change management approach support incremental PR integration?

Yes, each work unit yields a separate PR, enabling safer incremental integration and easier reviews for large-scale refactors and migrations executed across isolated git worktrees.

What are the limitations of parallel batch refactoring for large-scale changes?

Parallel batch refactoring requires changes to be decomposable into 5–30 self-contained tasks, meaning sweeping changes that cannot be isolated into independent work units with per-unit PRs and end-to-end validation are not suitable.