batch-operations

Batching applies identical or highly similar operations in parallel across multiple files or repositories. Group 3+ tasks together to reduce overhead, improve consistency, and execute them concurrently rather than sequentially, cutting execution time and manual repetition.

Use batching when performing 3 or more identical or highly similar operations—such as file edits, searches, test runs, or Git commands. Batching reduces overhead, ensures consistent results, and executes tasks in parallel, making it ideal for repetitive work across multiple files or repositories.

Yes, batching is operation-agnostic and handles file edits, searches, test runs, and Git operations. It applies batch-editor delegation and parallel tool calls to execute identical tasks across multiple targets, with validation checks and error handling built in.

Batch operations include validation checks, error handling, and batch indicators to ensure safety. A structured result-reporting schema captures outcomes, failures, and diagnostics across all batched tasks, letting you verify success and troubleshoot issues systematically.

Parallel tool calls execute multiple identical tasks concurrently instead of waiting for each to finish sequentially. This reduces total execution time and system overhead, especially when batching 3+ similar file edits, searches, or Git operations across multiple files or repositories.