batch-operations

First preview all matches with grep -rn to list affected files, then apply the replacement with sed on Linux/macOS or PowerShell on Windows. Afterward, confirm no old references remain and run the build and tests to catch breakage.

Use grep -rl to list files containing the pattern, then run find with sed -i for in-place replacement scoped by file glob. Always preview matches first and exclude directories like tests that may need different handling.

Yes. Locate all package.json files with a glob pattern, preview the current version strings, then replace them consistently across every file. Verify by grepping for the new version and running the install or build step.

Avoid batch operations for single-file edits, changes requiring per-file judgment, or replacements where context differs between matches. In those cases, edit files individually or delegate per-domain changes to separate review.

Breakage usually comes from overly broad patterns matching unintended text or skipping the preview step. Check git diff to review every change, narrow the pattern or file scope, and rerun tests after correcting.