Thank you! :) You are absolutely right on pre-commit hooks. My experience with FOSS projects is that it's quite hard to get contributors to follow your style guides and/or opt-in to pre-commit hooks. In this case it's much easier to have things auto-fixed than telling people to please install your specific pre-commit framework. It's different if you have a well-defined team with onboarding procedures.
FWIW, you can keep using pre-commit hooks and then have autofix.ci enforce them: https://autofix.ci/setup#pre-commit. For git purists, there's always the option to squash when merging. :)
