batch-operations

Sweeping Changes Across Many Files

When the same edit needs to land in dozens of places, treat it as a controlled operation: scope it, preview it, run it, then prove nothing broke.

Is This the Right Tool?

Fits well:

• Renaming a symbol everywhere it appears
• Dropping a shared import into a whole folder
• Synchronizing a version string across manifest files
• Stamping the same boilerplate onto a set of similar modules
• Swapping a deprecated call for its replacement repo-wide

Poor fit:

• A change confined to one file (edit it directly)
• Edits that differ from file to file (do them one by one)
• Anything needing case-by-case reasoning per file (delegate per area)

---

The Four-Step Loop

Step 1 — Pin Down the Change

Write the operation explicitly before touching anything:

Match:    [the exact token or pattern]
Becomes:  [the exact replacement]
Within:   [glob of files in scope, e.g. "lib/**/*.js"]
Skip:     [files to leave alone, e.g. "**/*.spec.js"]

Step 2 — Look Before You Leap

Always enumerate the impact first. Never start replacing blind.

# Which files contain it?
grep -rl 'oldName' lib --include='*.js'

# How many hits per file (drop the zero-hit files)?
grep -rc 'oldName' lib --include='*.js' | grep -v ':0$'

# See the actual lines, with line numbers
grep -rn 'oldName' lib --include='*.js'

Hard rule: surface the list of affected files to the user before you modify a single one.

Step 3 — Run the Sweep

Plain text substitution:

# Linux / macOS
find lib -name '*.js' -exec sed -i 's/oldName/newName/g' {} +

# Windows (PowerShell)
Get-ChildItem -Path lib -Recurse -Filter *.js |
  ForEach-Object { (Get-Content $_) -replace 'oldName','newName' | Set-Content $_ }

Anything beyond a flat find/replace — inserting imports, wrapping blocks, reordering — should go through the Edit tool per file, processed in a stable order (alphabetical, or following the dependency chain) so the run is reproducible.

Step 4 — Confirm It Held