It’s great. It’s become my preferred workflow for vibe coding because it writes great commit messages, gives you a record of authorship, and rollbacks use far fewer tokens. You don’t have to (and probably shouldn’t) let it push to the remote branch.
I'm glad that workflow works for you, I suppose. I let it edit files but not commit because I should have a full understanding and accounting of what changed, why, how, and what to commit.
