Would `git reset --hard` have worked to in your case? I guess you want to have each babystep in a git commit, in the end you could do a `git rebase -i` if needed.

Without git I would have been screwed. AI doesn't commit anything, I do when I'm satisfied

Ah, so you have not yet been forced to tell it DO NOT AMEND THE LAST COMMIT

Whatever settup I have in the office doesn't allow git without me approving the command. Or anything else - I often have to approve a grep because is redirects some output to /dev/null which is a write operation.

this has often saved me.

I simply disallow any git commands

"Hmm, it looks like I can't run git commands directly. I will quickly implement a small shell wrapper so I can commit."

this is sadly spot on

"well, it looks like I cannot run shell scripts, that’s strange. Let’s try implementing a git compatible vcs in rust"

  ln /bin/git fit
  ./fit

How do you disable commands?

One annoying thing about that flow is that when you change the world outside the model it breaks its assumptions and it loses its way faster (in my experience).

And accuses you of being a linter

To be fair to the model, I really can act like one sometimes.

Bam, now it did git reset --soft [initial commit] and force pushed to origin