PromptSharp › Prompt Library › Vibe Coding › One fix broke something else: find what the last change touched
One fix broke something else: find what the last change touched
The AI fixed the bug you asked about and now a different part of the app is broken. Find out what the change touched before asking for another fix.
The prompt — copy and run it
You are a careful senior engineer helping a non-engineer trace a regression caused by a recent change. I will paste the change (the diff or the AI's description of what it changed) and describe what broke. Produce: A) WHAT CHANGED — the change restated in plain language: every file, function, setting, or piece of data it touched, including anything the AI changed that I did not ask for. B) CONNECTION — how the broken feature could depend on the changed parts, with the specific link (shared function, shared data, shared style, renamed item). C) TEST TO CONFIRM — a check I can run myself: undo the change temporarily or test the broken feature with the old version, and what result confirms the cause. D) TWO OPTIONS — fix forward (a smaller change that keeps the original fix and repairs the new break) or roll back and redo the original fix more narrowly. When to choose each. E) GUARD — a short list of features to re-check after every change from now on. Inputs: [PASTE THE DIFF OR THE AI'S DESCRIPTION OF THE CHANGE] · [WHAT I ASKED FOR] · [WHAT BROKE AND HOW] · [MY LAST SAVE POINT] Rules: Do not invent code or connections not visible in what I pasted — ask for the specific file when needed. Treat every change I did not request as a suspect. Verify the cause with the confirm test before any new fix. Keep secrets and customer data out of anything pasted.
How to use this prompt
- Copy the full prompt above with the Copy button.
- Fill in your inputs. Replace each bracketed placeholder with your specifics:
[PASTE THE DIFF OR THE AI'S DESCRIPTION OF THE CHANGE][WHAT I ASKED FOR][WHAT BROKE AND HOW][MY LAST SAVE POINT] - Paste into ChatGPT, Claude, or Gemini and run. Read the reality guardrail below before you act on the output.
Why this prompt works
When a fix causes a new problem, the instinct is to ask for another fix, which often stacks changes until nobody knows what state the app is in. Listing everything the change touched, including unrequested edits, and confirming the link with a quick test identifies the real cause. Choosing deliberately between fixing forward and rolling back prevents a spiral of patches.
Get a prompt like this in your inbox
The PromptSharp Vibe Coding Brief ships one desk-ready prompt every weekday — free on the web today. Free forever. Today's Vibe Coding issue is live on the web right now — subscribe and we email you the sample issue immediately, then the Vibe Coding daily by email most weekday mornings, plus a Sunday roundup. Unsubscribe anytime.
Subscribe free → Read a sample issueWant the full PromptSharp Vibe Coding Brief, not just the free prompt? Vertical Pro is the full Pro benefit set for ONE vertical. See what Pro includes.
Card required. Free for 14 days, then $14.99/month — renews automatically until you cancel. Cancel anytime before day 14 and you won’t be charged. One free trial per card. Manage or cancel anytime.
Frequently asked
When should I use this prompt?
The AI fixed the bug you asked about and now a different part of the app is broken. Find out what the change touched before asking for another fix.
Why does this prompt work?
When a fix causes a new problem, the instinct is to ask for another fix, which often stacks changes until nobody knows what state the app is in. Listing everything the change touched, including unrequested edits, and confirming the link with a quick test identifies the real cause. Choosing deliberately between fixing forward and rolling back prevents a spiral of patches.
What mistake does this prompt help you avoid?
Stacking fixes on fixes: everything the last change touched is listed, unrequested edits are suspects, and the cause is confirmed before another change.
Related Vibe Coding prompts
Explain this code to me: a plain-English walkthrough before you change it
You need to change part of your app but you do not understand the code the AI wrote. Get a walkthrough you can follow so the next …
The debugging loop: reproduce, isolate, fix, verify — one step at a time
Something broke and your instinct is to paste the error and accept whatever rewrite comes back. Run the loop instead — one discipl…
Data model first: describe what your app stores before you ask for screens
You are about to ask an AI to build an app and you have only thought about the screens. Define the data first so the screens have …
Diff self-review: make the AI explain its own change before you accept it
The AI changed five files and you're about to click accept. Make it review its own diff like a skeptical outsider first.…
Dependency check: the packages the AI added, and whether you need them
The AI added several new packages to make something work. Check what each one does, whether it is needed, and what it brings with …
Incremental feature slicing: turn the big ask into small, verifiable builds
You want something big and the temptation is one giant prompt. Slice it into steps where each one runs, gets verified, and can't t…
Works on my machine, broken when deployed: a checklist that finds the difference
The app runs fine on your computer and fails after you publish it. Work through the differences between the two places one at a ti…
All Vibe Coding free prompts
The PromptSharp Vibe Coding Brief page — five full free prompts plus today's issue.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt most weekday mornings, plus a Sunday roundup, rotating across the roster. Two things in one brief: you get better at AI and prompting, and you see the sharpest prompts from across the network. If a day's issue misses our quality bar, we hold it instead of padding your inbox.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Even a sharp prompt starts from zero unless your AI knows you. Brainfile is persistent context — your work, voice, and priorities loaded into every session. Brainfile is the memory; PromptSharp is the playbook. Together they compound — the same prompt gets sharper because it runs on YOUR context.
Set up your brainfile →Want both? The All-Access + Brainfile annual bundle covers the pair.
Home · Daily Issues · Prompt Library · Glossary · Pricing · For Teams & Universities · Archive · PromptFluent alternative · Newsletter · Privacy · Terms · Refunds
Marketing · Sales · Dev & Engineering · Finance · Product Management · Vibe Coding · C-suite · Consulting & Strategy · Law · CPG · Personal Finance · Career & Job Search · Trading · Health & Fitness · Students · Focus & Productivity · Learning · Travel Planning
Entry Point Trading
Free weekly stocks to watch —
how our model ranks the S&P 500 and Nasdaq 100.