FREE RESOURCE · FROM THE "SCOPE" REEL
Small-change checklist: scope one edit so an AI coding tool changes one thing, not 24 files
By Hammad Yousuf · 1 November 2026
"Rename this button to Start, please." "Already building." One word, 24 files. The fix is not a better tool; it is a clearer request. Scope a small change clearly. Check the diff before accepting unexpected new features.
The small-change checklist
Run through it before you send any one-line change to Claude Code, Cursor or another AI coding tool.
Identify the exact element and intended change.
A vague target ("the button") lets the tool pick which button, and sometimes which page.
State existing behavior that must remain.
If you do not say what must stay the same, nothing tells the tool that a redesign is out of scope.
Request the smallest relevant change and an explanation for dependencies.
Asking for the smallest change, and for an explanation before any change outside the component, turns a silent rewrite into a question you can answer.
Inspect the diff and rendered result.
The diff is where you find the 23 other files. Read it, and look at the rendered result, before you accept.
Treat unexpected new features as separate requests.
A new feature that arrived uninvited is not a bonus; it is a separate request you have not reviewed yet.
The prompt
Swap "button label to Start" for your own element and change. The four instructions stay.
The small-change prompt
Change only the specified button label to Start. Preserve current behavior. Explain any necessary change outside that component before implementing it. Show the diff and verify the result.This can clarify scope; it does not guarantee model behavior.
Common questions
Why would an AI coding tool touch 24 files for a one-word change?
Because the request left room for it. A label change can be read as a chance to rename a component, update tests, add types or restyle the button. The checklist closes that room: name the element, say what must remain, and ask for the smallest relevant change.
Does this prompt work in Claude Code, Cursor and Copilot?
The wording is tool-neutral. Swap "button label to Start" for your own element and change; the four instructions (change only this, preserve behaviour, explain before touching anything else, show the diff) apply to any AI coding tool. It can clarify scope; it does not guarantee model behaviour.
What should I look for in the diff?
Files you did not expect to change, new dependencies, renamed functions or components, and any behaviour that differs from what you said must remain. Then look at the rendered result, not just the code.
The tool added a useful feature while it was in there. Should I keep it?
Treat it as a separate request. Revert or set it aside, then ask for it on its own so you can review it with the same care as the change you actually asked for.
About the video: the reel that sent you here is presented by an AI avatar of Hammad Yousuf; the script and the checklist are his.