this post was submitted on 14 Oct 2025
9 points (71.4% liked)
Programming
23631 readers
148 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This sounds similar to "Static code analysis" tools. Especially now that these code analysis tools are getting AI integrations.
For example we use coderabbit.ai. That does a code review on PRs in github, and reviews these sort of things. Especially the simpler things that you've mentioned like poor naming conventions, violations of language-specific best practices, and readability issues. I'm not sure if it will automatically come up with "large refactoring opportunities" by default - but maybe you can custom-prompt configure it to try, I guess
Coderabbit also has IDE extensions: https://www.coderabbit.ai/ide - I think the separate webpage exists for org level configurations and overviews. These "best practices" are probably defined on a team level to ensure everyone uses the same code-style and things like that
I'm not sure if "just a website to copypaste code and get reviews" is really a good idea. Maybe for juniors that want to review one class or method or something. But usually code is spread across multiple files, and structural refactor opportunities are on a larger scale then just a couple files
Hi, thanks for sharing the info, appreciated