All ideasMore in Work
Work

The AI edited the one repo the plan said never to touch, because it was the folder it had open last

During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.

This one went wrong. Read what happened so you don’t hit the same problem.

How it works

  1. Plan states the legacy repo is not to be touched
  2. Plan re-shown in full mid-session
  3. User asks for a follow-up change
  4. The AI searches its most recent folder, the fenced repo
  5. Edits a matching file there
  6. User catches it
  7. Edit reverted and redone in the right repo

Why it’s worth knowing

The rule was not buried. It had been put back in front of the agent in full, in the same session, shortly before the edit.

Where it’s from

Summarized from a public post on github.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

WorkFind me 48 school-district customers and draft each pitch — one replied, booked and paidWorkThe AI audited my eBay store, found 28 listings going nowhere, and sold a bundle for meWorkRead every job advert, tailor my CV and apply with my approvalWorkFive years of books rebuilt from 34,000 transactions across 27 statement formats

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.