I don't plan my commits but think it's a good idea for certain types of developers. I find that testing really helps me define commit borders. For instance, I'

I don't plan my commits but think it's a good idea for certain types of developers. I find that testing really helps me define commit borders. For instance, I'll often commit once each new endpoint is tested, new class (if small) is tested, etc. Testing is great because it defines a natural place to commit (once the tests pass and the tests describe the functionality). However, some things aren't tested (shame on me) and I find myself saying to commit once something is working. Keeping a clean working tree is critical to me. As is using a visual commit tool. I often see better commit messages and chunking done with visual committing