Alternatives
Products that do what Veridu does
Better code review. Two reviewers, not one.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14IB
I’ve spent the last 2.5 months building a product that runs LLM-powered code reviews on my pull requests — and I just launched it. The tool is built specifically for solo developers. You install it on your repo, trigger a scan by creating a pull request, and it leaves structured review comments using OpenAI under the hood. Funnily enough, I used the dev version of this app to review its own pull requests while building it. It helped me spot bugs, simplify structure, and keep quality high — all with minimal need for another human in the loop. Things I want to try out in the next months : -…
2025 · codii.dev
- 15
- 16
- 17
- 18BY
Hey HN - We're building wispbit (https://wispbit.com/) - a tool that lets you build your own AI code reviewer. We built this because we worked in big and complex codebases where we kept hitting booby traps - often the same ones. People forgot things, or quit altogether, amplifying the problem. We looked for other ways to fix this, but the solution is usually a combination of: - Writing a linter rule - too difficult and time consuming. - Writing docs and having frequent meetings on alignment - basically a full time job. - Using plug and play code reviewers - too generic and…
2025
- 19OS
Hey again HN. Isaac and I originally released a voice-first code review tool, but have since open-sourced it and turned it into just a better way to review your and your team's Github PRs. Main things we've heard that make code reviews slower are: 1) PRs are too big and overwhelming 2) Need to jump around to find the right context and relevant code 3) Need to spend time thinking (should not be a thing since AI exists), and writing comments What we built to address these: 1) PRs are split up into sub-PRs without needing to actually split them up and stack them yourself -> Automatically done…
2025 · github.com
- 20AC
This week we released the Kodus CLI. It took a bit longer than we expected to ship. The reason was simple: there are already many ways to run reviews locally today. IDEs, extensions, terminal commands, agents inside the editor. So building “just another AI CLI” didn’t seem like a good idea. The question that guided the project was different: how can we bring the quality of PR reviews to the moment when the code is still being written? Today the CLI does two main things. The first is running local reviews using the same context we use in PRs. The goal was to avoid that shallow review that…
Mar 2026 · github.com
- 21
- 22RA
I built r3 to scratch my own itch when reviewing long design doc and planning doc from AI. The chat interface is inherently bad at tracking multiple pieces of feedback across different parts of a document, so I created a lightweight local web UI to organize the review process. I have been using it on my own projects for one week, and it has made giving structured feedback to AI much easier. I thought others working with AI coding agents might find it useful too. I'd love to hear what you think and any feedback you have!
Jul 2026 · github.com
- 23CB
2021 · codeapprove.com
- 24AC
Hey HN! I’m Julien, the founder of Code Inspector, a platform that helps developers and managers produce better code and reduce technical debt. We would love to get some feedback from the Hacker News community. Our platform inspects code, looks for defects (security, vulnerability, design, performance, lack of documentation), automates code reviews and reports on team activity. You can customize violation alerts to reduce false positives. We currently support GitHub, Bitbucket and Gitlab. I’d love to hear your thoughts on what you would expect from such a platform (what you like, dislike)…
2021
Ranked by how close each launch is in meaning, then by votes. Refine with a description →