I work on a project where we recently heavily pivoted into AI assisted feature development and without a extremely defensive/aggressive lint config and test coverage near ~80% most of these developments would be quiet impossible.
`no-reflect-get` is definitely one I'd adopt, claude LOVES `Reflect.get` for some reason
oxlint and some general ast-grep rules have pretty much been an absolute necessity for any of my LLM based code generation. I started down this path after looking at what coderabbit suggested in https://github.com/coderabbitai/ast-grep-essentials
I work on a project where we recently heavily pivoted into AI assisted feature development and without a extremely defensive/aggressive lint config and test coverage near ~80% most of these developments would be quiet impossible.
`no-reflect-get` is definitely one I'd adopt, claude LOVES `Reflect.get` for some reason
A lot of the lint rules in this repo remind me of https://github.com/sindresorhus/eslint-plugin-unicorn, I can't wait until oxlint has plugin support so I can move over to it.
I think oxlint ships unicorn as a plugin to enable --> check into that
But if any others, let me know, and feel free to make a pr!
I agree https://github.com/dmmulroy/anti-slop is very cool (heard about it via https://www.youtube.com/watch?v=ix1qQK1IvmA).
But what does this add beyond that?
oxlint and some general ast-grep rules have pretty much been an absolute necessity for any of my LLM based code generation. I started down this path after looking at what coderabbit suggested in https://github.com/coderabbitai/ast-grep-essentials
I really believe having good rules like this can make a big difference in llm quality. So this is awesome thanks.
I’m personally using both oxlint for typescript and my own vibe coded tool for doing cross language rules ast rules and llm hook outputs.
And recently added vale as well.
Awesome. Feel free to make a pr for any rules that you think are important. I've started adding to my friends sloppy codebases and its great!