parallel-edits

Multi-file code refactors are coordinated by planning exact old and new string pairs across affected files, reading targets in parallel to validate content, and executing synchronized batch edits that preserve indentation.

Consistent import updates across multiple files are applied using a plan-read-validate-execute workflow that reads target files in parallel, verifies exact string matches, and executes all replacements in a single synchronized batch.

Yes, read-before-write validation reads all target files in parallel to verify exact content and ensure edits are applicable before any changes are executed, preventing mismatches and failed replacements.

Parallel batch editing preserves exact indentation and file structure during large-scale renames by enforcing strict uniqueness or replace-all strategies when applying coordinated edits across multiple files.

A plan-driven workflow should be used for multi-file edits when changes must remain consistent across many files, such as module refactors or import updates, requiring all affected files and exact string pairs to be identified beforehand.

Parallel edits require exact old and new string pairs to be defined beforehand and rely on strict uniqueness or replace-all strategies, meaning ambiguous string matches without clear validation will cause batch execution to fail.