A small Claude Code habit that has saved me from some very unnecessary diffs
I’ve started asking Claude Code to show me the files it expects to change before it starts making edits. Not a full plan. Just the expected scope. For example, if I’m fixing something in one API endpoint and Claude says it expects to change the controller, service and one test, I already have a rough idea of what the final diff should look like. If it suddenly touches a config file, a shared utility and three unrelated modules, I know to stop and check what happened instead of discovering it at the end. It doesn't prevent Claude from making a bad change, but it makes unexpected scope much easier to catch early. For larger tasks I still let it work across the project. I just like having a rough boundary before the edits start.
评论
?
参与讨论