This, I'm working on a game engine as a hobby project. I can do one "big" feature over a weekend, most of it including designing and manual testing that it's working as expected, but then it takes me 2 weekends to break up the changes into smaller commits using jj, which also gives me the chance to review and understand the code myself. So it's a weird mix of fast and slow, but I think I've grown to prefer reviewing over writing so it works for a hobby project.

> …but then it takes me 2 weekends to break up the changes into smaller commits using jj, which also gives me the chance to review and understand the code myself.

I just tell Claude Claude code, "commit all, grouping logically" after a tranche of work.

Genuine question a why are you using AI for a hobby project like that? It seems like the worst of both worlds.