Yeah, sometimes I love it when it checks the git log and properly finds reference code for what I’m trying to implement, but other times I really want it to just do it differently and can get annoying

Other times I’ll tell it about an issue that I want to solve and it will come up with a solution I don’t want. I’ll tell it to take a different approach and it will listen for a bit, then all of a sudden just try to go back to its first approach and I need to steer it again, multiple times even

> but now I have to write a message each time to keep track of which is which

I ask it to write my commits. Usually it’s also pretty smart about which files to include based on the most recently addressed tasks. I have it run git add and git commit under my supervision

A repo Im working on, has some rather annoying hooks that check linting when committing (and aggressively modify the files to fix formatting). If I forget to manually check before committing, then I end up with a “wrong” commit containing the incorrectly formatted files, and a bunch of uncommitted files with the formatting changes. CC most of the times will see the error messages, and automatically propose the proper commands to run for undoing or amending the commit to include the formatting changes

My commit messages have always been crap, so this doesn’t bother me much. I squash it all at the end anyway.

Still sometimes I forget to commit between tasks or it goes wild fixing compiler errors I didn’t want to address.