We're using husky git hooks in combination with commitlint according to https://commitlint.js.org/#/concepts-commit-conventions:
type(scope?): subject
body?
footer?
Type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]
source: commitlint documentation
If you'd like to test your commit message previous to using it, you could test it on the command line:
echo 'foo: bar' | commitlint
The general code conventions are guaranteed by the following tools.
Both the .editorconfig and .gitattributes ensure a consistent code structure and conventions through their configurations.
The xo tool provides a general code linting mechanism.
The prettier tool provides a general code prettfying.