What problem does it solve?
Ensures multi-file changes are applied atomically and consistently so that related edits (like API version bumps, import adjustments, or configuration updates) never leave the codebase in a partially-updated or broken state.
Core Features & Use Cases
- Manifest-driven edits: define edit/create/delete steps in a structured manifest for deterministic execution.
- Safety-first workflow: perform a dry-run to confirm exact matches, execute only if all checks pass, run verification commands, and automatically roll back on failure.
- Practical use cases include API version migrations, coordinated refactors across modules, bulk renames, and creating/deleting related files as a single operation.
- Built-in constraints and limits include text-only edits (no binaries), per-file size/line limits, and workspace path restrictions to prevent accidental external changes.
Quick Start
Apply a batch-edit manifest that replaces API version "v1" with "v2" across the workspace, run the dry-run to confirm exact matches, execute the changes atomically, and verify that no "v1" occurrences remain.