Related to the article: I noticed a lot of style like nits that ESLint didn't cover, but also weren't necessarily worth pausing and writing an entire ESLint rul

Related to the article: I noticed a lot of style like nits that ESLint didn't cover, but also weren't necessarily worth pausing and writing an entire ESLint rule for. So I wrote checkr: https://github.com/ELanning/checkr https://github.com/ELanning/checkr which lets people plugin simple ad-hoc regex check lints (and underlines them in VS Code + git pre-commit check). Hopefully to help break the endless cycle of code review nits that may be specific to your project.