[number6]

As someone whos commit message are: fix, fix again, this hopefully works, again.

I am sure AI cannot even glims the frustration I feel committing these commits.

You can argue, that these messages are as poor as the code that I have written; but don't tell me you haven't been there -- and if you have please tell me your secret

[skydhash]

My secret is intent (and magit). If I’ going to write code, I already have a few goals in mind. That’s what I put in the commit message. Magit is for I did other stuff, so I can stage individual hunks/lines instead of whole files.

[nextaccountic]

My favorite git command is git commit --amend, my second is git rebase. Until you push, you don't need to keep adding new pointless commits

Actually I wish that we had two branches in parallel, one with cleaned up commits, another with how the software were actually edited. But we need tooling for that

[Izkata]

If you go all the way to where the cleaned-up version is a squash merge, as so many unfortunately do, we already have that: regular, non-squashed merges.

If you don't go that far, you could mimic something like it with sub-branches and merge commits for each one into your working branch, but I imagine it would be annoying to handle at that granularity.