batch

Decompose codebase-wide modifications into parallel git worktree units with automated testing and pull requests.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/rysweet/RustyClawd --skill batch-rysweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch
Source: https://github.com/rysweet/RustyClawd/tree/main/.claude/skills/batch
Command: npx skills add https://github.com/rysweet/RustyClawd --skill batch-rysweet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of making significant, widespread changes across a codebase by breaking them down into manageable, parallelizable units.

Core Features & Use Cases

  • Decomposition: Breaks down complex changes into independent, testable units.
  • Parallel Execution: Runs multiple units concurrently in isolated worktrees for speed.
  • Automated PRs: Creates pull requests for each completed unit.
  • Use Case: Refactoring a core library, migrating a feature across many services, or applying a consistent code style update throughout a large project.

Quick Start

Use the batch skill to add structured logging to all HTTP handlers in the project.

Frequently Asked Questions about batch

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

FAQPage Schema
How do I automate large-scale codebase migrations across multiple services?

Large-scale codebase migrations are automated by decomposing modifications into independent, parallelizable units executed in isolated git worktrees, followed by automated testing and pull request creation for each unit.

Can I run parallel refactoring tasks without creating git branch conflicts?

Parallel refactoring runs in isolated git worktrees to prevent branch conflicts, concurrently executing independent code units while maintaining a clean working tree for each operation.

What do I need to set up before automating bulk code modifications?

Automating bulk code modifications requires git, the gh CLI, and a clean working tree to manage isolated worktrees and create pull requests successfully.

What is the best way to apply a consistent code style update throughout a large project?

Applying a consistent code style update throughout a large project is best handled by breaking the widespread changes into independent, testable units that run concurrently and generate automated pull requests.

When should I not use parallel worktrees for codebase refactoring?

Parallel worktrees for codebase refactoring should not be used when your working tree is unclean, or when the code modifications cannot be decomposed into independent, testable units.

How does batch handle codebase-wide pattern application and refactoring?

Batch handles codebase-wide pattern application by decomposing refactoring tasks into independent units, executing them concurrently in isolated worktrees, and automating pull request creation.