Personally I’ve been using

pre-commit

as a git-hook to ensure branching naming schemes, not committing to main, large files and etc and

MegaLinter

for PR checks to check against linters for specific languages used in the repo. And MegaLinter can be implemented in your CI process as well and posted to your PRs to ensure you’re meeting your standards you want to set. And it will cover majority of what is currently used right now. Like most things when it comes to ensure tech debt, it takes time to get buy-in from the engineers but I’ve found it to be great and to help with keep tech debt to a minimum. Links: https://megalinter.io/latest/ https://pre-commit.com

This is something we put together a while ago

those are helpful resources thanks guys

Thanks everyone for the contributions. There's some great bedtime reading in here 🙂 Really appreciate you all sharing.