Fix · Problems with AI tools

How do I go back to the version that worked? (rollback plan)

Blocks your work

What you may see

Everything worked this morning and now it is broken
I want to undo the last AI changes

Most likely cause

If your work is saved in Git, every saved step can be restored; the safest way is to look first, make a safety copy, then go back.

Check first (about two minutes)

Is the project in Git, and do you have commits from the time it worked? Run git log --oneline -15.
Do you have edits that are not saved yet that you want to keep? (git status)

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who reviews work done by AI coding tools, keeps projects safe, and explains everything to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

THE PROBLEM
How do I go back to the version that worked? (rollback plan)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
If your work is saved in Git, every saved step can be restored; the safest way is to look first, make a safety copy, then go back.

DO THESE STEPS, IN THIS ORDER
1. Show git status and git log --oneline -15. Help me identify the last commit that worked, by date and message.
2. Make a safety copy of the current state first (a branch named backup-before-rollback, including unsaved edits committed there).
3. Show me the difference between the good commit and now (git diff --stat <good> HEAD), and explain it.
4. Give me the options: (a) undo everything back to the good commit, (b) undo one file only, (c) keep my work and revert only the bad commit. Recommend one and wait for my choice.
5. Do the chosen option with the safest commands, and run the build to confirm.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The app works as it did at the good commit, and the backup branch still holds the broken state for later study.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not use git reset --hard before the backup branch exists.
- Do not touch the database or live data: a rollback of code does not undo data changes.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Show git status and git log --oneline -15. Help me identify the last commit that worked, by date and message.
Make a safety copy of the current state first (a branch named backup-before-rollback, including unsaved edits committed there).
Show me the difference between the good commit and now (git diff --stat <good> HEAD), and explain it.
Give me the options: (a) undo everything back to the good commit, (b) undo one file only, (c) keep my work and revert only the bad commit. Recommend one and wait for my choice.
Do the chosen option with the safest commands, and run the build to confirm.

Do not do this

Do not force push to a shared branch to "clean" history.
Do not use git reset --hard before the backup branch exists.
Do not touch the database or live data: a rollback of code does not undo data changes.

Try another entry