For typo checks you should use GitHub - crate-ci/typos: Source code spell checker. I’m using it almost every day and it simply works every time.

It even has a GitHub action if you don’t want to only use it as an offline CLI tool (which is how I use it exclusively but a GitHub action is super useful for CI/CD).

This could be another alternative:

I’ve never personally tried it but the maintainer is a friend of mine and he told me it’s generic so it should work on any type of repo.

I think this should be highlighted, as this is the silver lining. Such tools are just linters on steroids, even though I doubt they are that consistent, it would be a mistake to assume that they can replace the human factor in code reviews.

I also think it’s also important to point out that this might be a shortcut for companies that never understood how to setup and use already existing static analysis tools like credo (especially with custom made check rules).

i wrote my own (corerev.q32.com), here’s why:

i want it to:

• inline comment
• draft only
• in my name (for me to look at and approve/change/edit)

this:

• gives me focus
• saves me time

i use it every day.

Never tried out anything similar , but it looks like it could be useful. Just installed it on our repo. My first impression is that is is quite noisy e.g. chore: Convert login page to react by shiroyasha · Pull Request #1638 · operately/operately · GitHub, but maybe I have to get used to it.

Did your team leave all the config options enabled or you made some modifications?