What problem does it solve? Bulk find-replace operations, file renames, and path relocations silently corrupt repositories: references built from path.join segments survive rewrites, URLs get accidentally rewritten, half-converted paths break at runtime, and zero-hit greps produce false conclusions about absent tokens. ## Core Features & Use Cases - Rename sweep mechanics: Rules for scoping string replacements so target-namespace files are not double-prefixed and external URLs containing the old path string are not rewritten. - Post-rename verification: Techniques for catching references that survive a mechanical pass, including searching individual path segment tokens, matching slashed and bare path forms, and running the test suite as the real detector. - Search correctness: Guidance on case-insensitive greps, git pathspec exclusion instead of grep -v filtering, git ls-files for structural checks, and anchored text edits for hand-maintained JSON configs. - Use Case: When renaming foo/ to bar/foo/ across a repo, apply these rules to avoid double-prefixing, catch path.join-constructed references, and verify with tests before committing. ## Quick Start Before doing a bulk rename of the utils directory across this repo, apply the repo-text-sweeps rules and verify no references were missed afterward.
