Stop Claude Code From Changing Things You Never Asked For: Set Up the /bouncer Skill in 2 Minutes
Ask Claude to fix one thing and it quietly changes twenty others, and days later your app breaks and you can't tell which edit did it. This free Claude Code skill puts a bouncer at the door: Claude lists everything it plans to touch, checks each item against what you asked, and only the ones that pass get made. How to set it up, ready-made prompts, and what an answer looks like
Ask Claude Code to fix a login button and it may also rename files, restyle pages, upgrade packages and tidy things you never mentioned. Each one is small. Together they are why your app breaks two days later and you have no idea which edit did it.
This skill puts a bouncer in front of those edits. You type the task, and nothing gets changed that the task didn't need.
What /bouncer does
- THE ASK: Claude writes what you asked for in one sentence. That is the only thing allowed through the door.
- THE LIST: before it edits anything, Claude writes down every change it is thinking of making, including the tempting extras.
- THE DOOR: each item is checked against the ask. Needed to do the task is a tick. Not asked for, or the task works without it, is NOT ON THE LIST.
- Only the ticked changes get made. Then you get a short report: what was done, and what was turned away so you can say "yes, do that one" if you want it.
It is a rule Claude follows when you call it. It is not a lock, so skim the list before you let it carry on.
Keep reading
Free, for an email.
Unlocks 5 more sections, 8 copy-paste prompts, the document version, and every other guide on the site, for free. Enter your email once to keep reading.
19,000+ follow where these guides come from.No spam. Unsubscribe in one click.