What you’ll make
Rename two files safely in a copy and save the before-and-after names.
Worked example
Rename two files in a sound effects pack
Your working copy has eight WAV files. Both “door-final.wav” and “door-final-copy.wav” could end up with the same name. You listen to both and decide which take belongs in the pack.
Claude Code proposes a rename table. You approve the door close and a footstep for the first batch, then play the renamed files to check that the contents still match.
Before you start
- Choose a low-stakes folder and make a working copy with a handful of representative files. Include one ambiguous file and one pair of names that could collide. Keep an untouched original for comparison.
- Install Claude Code with the instructions for your operating system and sign in with an eligible account. Open the terminal in the working copy or choose it in Claude Code Desktop.
Make a copy and pick two files
Duplicate a small folder in your file browser. Open the copy, choose two files you recognize, and write down their current and proposed names. Leave the original where it is.
I copy my eight WAV files and listen to both door takes. I pick the approved door close and one wood footstep.
I have two specific files to rename, and I know which alternate take to leave alone.
Preview the renames in Claude Code
Open Claude Code in the practice copy. Paste the prompt with the copy’s full path, the two source names, and the new names. Ask for the read-only table and compare the paths and filenames with your file browser.
I give Claude Code the approved source names and ask for door-close-01.wav and footstep-wood-01.wav.
I expect a row for each file. If a destination already exists, the table should flag it so I can resolve the collision.
Preview two file renames in my practice copy
Review a small file rename in my practice copy. Use the details I provide in this chat or in my attachments. Keep this run read-only. Confirm the actual working path matches the copy path I supplied before inspecting it. Check only the files needed for the proposed renames. Return one table with the current name, proposed name, and any reason to pause, including a missing source or an occupied destination. Flag an alternate take or ambiguous match for me to resolve. Ask for the exact copy path or source names if you can’t confirm them. Leave every file untouched.
Rename the two files in the copy
Once you’ve reviewed the table, make the two renames in your file browser. Keep the extension, stop if a destination already exists, and save the old and new names so you can reverse the change.
Open both files before you finish
Open or play the renamed files and compare them with the originals. Check that the skipped file is still there and that the count in the copy matches the starting count.
- The new names match the two rows you approved.
- The renamed files still open or play.
- You saved the mapping with both original names.
Optional: Try a filename that would cause a conflict
Make a new practice copy and include two files that would end up with the same name. Ask for a preview and check that it calls out the conflict before any changes.
Show me what would change in my sample folder
Run this from your working copy to inventory files and preview one small batch before editing anything.
I’m in a copy of my business folder and want to [one file task]. Confirm the actual working path matches [expected copy path]. Inspect only [subfolders and file types] and report the count and any skipped locations. Keep this run read-only. Stop if you can’t confirm the copy path or an item points outside it. Show a table of relative paths, extensions, proposed paths or outputs, and the rule behind each change. Flag existing destinations, case-only changes, shared base names with different extensions, and references you find in the available files. Mark uncertain classifications for me to decide. Suggest two or three rows for a first batch and give me the checks to run in my file browser. If you can’t inspect a file or dependency, tell me what evidence is missing and keep it out of the proposed batch.
Apply the exact rows I approved
Paste the reviewed mapping to apply the small batch and get a record you can reverse.
Work inside [verified copy path] and apply only [approved rows and operation]. Before changing anything, recheck each source, destination, and the approved batch size. If a source disappeared, a destination exists, or a path escapes the copy, skip that row and tell me what happened. Preserve file contents for moves and renames. Keep completed and skipped rows in the results, including the original path and final path for each change. Report before and after counts, the checks you ran, and a reverse mapping for completed rows. Tell me which changed file and skipped file to open myself.
Troubleshooting
Why did two proposed names collide?
Choose the canonical file with a quick visual comparison, add a documented variant suffix if both belong, and regenerate the preview before applying either rename.
What if the session asks to work in another folder?
Check the current path and start a new session from the working copy. If the job genuinely needs another source, add a relevant copy to the sample folder and rerun the inventory.