I like to prevent bad commits. I only wonder if this could be a contributor barrier.
I'm fine either way so I defer this one to the others.

I think everything that keeps the code base clean and tidy is worth a look and try. I don't think that the additional check doesn't introduce a barrier for contributors.

I just ran into lint-staged which can be used to lint (and --fix) files before committing which might be of use: https://github.com/okonet/lint-staged

I just love the idea of this check @zaggino 👍. I don't think it's going to slow down development as any sanity check failure has to be worked on immediately to pass the build. So either we work after a bad commit or while doing it. But this check can at least save a bad commit. I am all in for this 😄 .