[samuraiseoul]

At my employer we started using Codacy a few months ago, providing things like that are what you're asking.

Things were real touch and go for a while with the analysis taking forever or other problems but they released an update a few months ago and that's not much of an issue at all now. We had one other issue with the integration with GH where the person who signed up for it left the company and our integration went to hell but we've fixed that and it was our fault. Just be sure the account that is the repo owner is the one registering, not a contributor.

We haven't tweaked the settings as much as we need to but it's been nice. It catches things and links to education so the reviewer can focus on more important pieces like the architecture or other things. The settings are very granular so you can turn some on or off depending on preference. Another nice thing about Codacy at least(haven't used others) is that many of the things it complains about has explanations or links to good explanations and the why, so that the person can learn as well as fix, hopefully preventing further mistakes of the nature in the future.

Overall I think that Codacy and things like it are great tools. But for sure linting and static analysis can be at least slightly done with git hooks or CI tools as others said if you want a poor man's kind of trial run. I hope that helps!