Safe Bulk Rename Planner
Preview, apply and undo manifest-driven renames with lexical symlink checks before any rename or journal write.
The problem it solves
Safe Bulk Rename Planner Safe Bulk Rename Planner previews regular-expression filename changes, rejects collisions and unsafe destinations, and can produce a hash-bound JSON manifest before anything moves. Applying a reviewed plan uses two-phase renames, and the same manifest can undo the operation while the files still match their recorded content.
Who Safe Bulk Rename Planner is for
- People who need a small, purpose-built utility instead of a broad platform.
- Users working with files, rename, preview who want the documented v1.1.1 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Preview, apply and undo manifest-driven renames with lexical symlink checks before any rename or journal write.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.1.1
Capabilities below come from the current project README and release documentation.
Safe Bulk Rename Planner previews regular-expression filename changes, rejects collisions and unsafe destinations, and can produce a hash-bound JSON manifest before anything moves. Applying a reviewed plan uses two-phase renames, and the same manifest can undo the operation while the files still match their recorded content.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Verified release evidence
This project does not currently publish a screenshot or dedicated example folder. The current README, tests, changelog, tagged release, and source repository remain the verified examples of its behavior.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
- macOS
- Linux
Built with
- Python
Changelog
Release notes from the canonical v1.1.1 source tag.
Imported manifest paths are inspected in their lexical spelling before resolution. A symlink at a source, destination, root or ancestor is rejected before any rename or journal write. Containment, original-directory, Unicode/case collision, size and SHA-256 checks still apply. Normal apply/undo and read-only interruption inspection remain available. Use disposable trees for tests. Concurrent filesystem replacement remains outside the guarantee; this check does not make renames atomic or provide automatic recovery.
- Repair formatting and add visual per-file selection, Unicode/case collision review, interruption journals and read-only recovery inspection.
- Added regression coverage for the audited behavior and invalid inputs.
- Added non-destructive regular-expression rename previews.
- Added collision, traversal, symlink, size, and SHA-256 safety checks.
- Added manifest-required application and content-verified undo through two-phase renames.
- Added recursive opt-in, tests, packaging, and cross-platform CI.
Quick start
The shortest documented path into the current release.
Preview spaces changing to dashes:
rename-plan "C:\Downloads\Review" --match "\s+" --replace "-"Save and apply the reviewed plan:
rename-plan "C:\Downloads\Review" --match "\s+" --replace "-" --output rename-manifest.json --apply
rename-plan --undo rename-manifest.jsonPreview is the default. --apply is refused without an output manifest. The planner handles files only, ignores symbolic links, keeps each rename in its original directory, and supports --recursive when explicitly requested.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
- Existing targets, duplicate destinations, path separators, and traversal attempts are rejected before any rename.
- File size and SHA-256 must still match before apply or undo.
- The manifest records filenames and hashes; treat it as local operational data when names are sensitive.
- The tool does not rename directories, edit file contents, transliterate text, or guess naming rules.
- An operating-system or hardware failure during a rename can still require recovery from backup.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
No privacy behavior beyond the current repository documentation is claimed. Review the source, security policy, and input/output behavior before using sensitive material.
License and release
Safe Bulk Rename Planner is published under MIT. The current cataloged release is v1.1.1, published 2026-10-16.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Safe Bulk Rename Planner v1.1.1
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: f1ea2401f0237d7f.