While I might choose slightly different tooling and configuration, this closely matches my practices. In particular, I'm a big fan of the pre-commit hook for li

While I might choose slightly different tooling and configuration, this closely matches my practices. In particular, I'm a big fan of the pre-commit hook for linting/testing/etc. automatically and preventing a commit if they fail (you can always override it if there's some rare emergency). Another thing I like to do is create a skeleton project and keep it in Git, so that this stuff doesn't have to be done manually for each new git project. You can check out/fork/clone/whatever the skeleton and have most of this stuff pre-configured, including e.g. a baseline requirements.txt for whatever frameworks you use. You can also put the pre-commit stuff into a ~/.git_template so that newly-created repos already have it configured. It's a bit harder to manage if you work with multiple unrelated languages/frameworks, but can be a real time-saver in a uniform environment.