When your git commit history gets long in the tooth, and you want to clean up your feature and topic branches before the merge to master, you’ll need the facilities of the Git squash commit feature.

With UI-level access to this Git power-user feature, more teams are squashing commits to make code review easier and provide a cleaner-looking history in tools like gitk or SourceTree.

However, automatically squashing seems kind of dumb. You can't automatically clean up a private history and turn it into a single, logically coherent commit, with a coherent commit message.