Rename That Missed File 13
by•
I asked Claude Code to rename a function across the codebase. It found 12 files, made the change confidently, and reported success.
What it missed: a thirteenth file in a directory outside its initial search scope. No warning. The app kept working because that file only ran on a rare edge case. I caught it three days later during an unrelated test.
Now I run a manual grep after any multi-file rename. What's your "agent confidently missed one thing" story?
4 views
Replies
Mine was the opposite risk. When my app changed its name, the instructions for the agent had to say what not to rename as much as what to rename: the package name, the bundle id, the old link scheme and the sign in link domain all stay as they were, because those are identity, not copy, and existing installs and the store listing depend on them. A confident rename across the whole codebase would have hit those too. So for any rename I'd write the list of what stays first, then add your grep at the end: every hit of the old name that is left should be on that list.