Alternatives
Products that do what Code reviews intimidated me, so I built a course on how to master them does
I’m excited to share Master the Code Review: forge a better process, give better reviews, write better code. It’s a video course with 4+ hours of content [1]. I’ve linked a 21-minute sample below [2]. 6 years ago, I began my software engineering career at Amazon Web Services. I struggled with Pull Requests. My authored PRs received many comments, sometimes 50+. They went through many revisions, sometimes 7+. I often shipped late. My reviews of other PRs were surface level and counterproductive. Long story short: I improved. Through trial, error and experience I learned how to be effective in…
- 1SP
Hey HN! We're Charles and Dean, and we're building Stage: a code review tool that guides you through reading a PR step by step, instead of piecing together a giant diff. Here's a demo video: https://www.tella.tv/video/stage-demo-1pph. You can play around with some example PRs here: https://stagereview.app/explore. Teams are moving faster than ever with AI these days, but more and more engineers are merging changes that they don't really understand. The bottleneck isn't writing code anymore, it's reviewing it. We're two engineers who got frustrated with…
Apr 2026 · stagereview.app
- 2
- 3
- 4
- 5
Practice code reviews like a senior engineer
Jul 2026 · code-review-sandy-phi.vercel.app
- 6
- 7PR
This year I’ve reviewed more than 1000 code changes. Most of the time was spent catching obvious mistakes rather than debating complex design decisions. If we estimate ~10 minutes per review, that’s 160+ hours spent reviewing code in just one year. So I thought: could I get some of that time back using LLMs? That's why I spent the last few weekends building an LLM-based prereviewer that should take a first pass before the actual human reviewer. The results so far are promising: I estimate it can reduce the review time by 50%, which in my case would mean I save 80hours (~10 working days) per…
2024 · github.com
- 8OS
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
- 9
- 10LC
2014 · hangouts.readthesource.io
- 11AS
Create a review as you would on pastebin, then any line in a review can be clicked to leave a comment. Comments appear under the line they reference and can be hidden by clicking the red tabs on the left or right. You can optionally toggle all comments by clicking the speech bubble at the top of the review. You don't have to have an account to create a review or leave a comment. I plan on adding multi-file reviews as well as version control access in the next few releases. After that I plan on making some IDE plugins to allow users to send code directly to the site via their IDE. Let me know…
2012
- 12IB
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
- 13OS
Hey HN, Over the last year, I’ve reviewed more than 1000 code changes. Most of the time was spent catching obvious mistakes rather than debating complex design decisions. If we estimate ~10 minutes per review, that’s 160+ hours spent reviewing code in just one year. So I thought: could I get some of that time back using LLMs? That's why I spent the last few weekends building Presubmit.ai, an open-source AI reviewer that runs as a Github Action right when you open a Pull Request. The results so far are promising: I estimate it can reduce the review time by 50%, which in my case would mean I…
2024 · github.com
- 14CA
Nowadays I review a lot of code locally that was written by llms. I used to review my own code using git + delta. It started to feel limiting with the amount of code written by llms. When looking at a large diff on Friday I pointed an llm at diffs.com and trees.software and told it to build an app. It only took 16 minutes, is extremely fast for large diffs, beautiful and minimal. Today I polished it up and added all the features that I need. It has file filters, search, an llm walkthrough mode, and review comments that you can paste back into your llm. I will be using Codiff a lot, and can…
May 2026 · github.com
- 15AC
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
- 16AC
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
- 17
- 18
- 19YA
2019 · github.com
- 20GA
hi, TLDR: I’m a programmer/solopreneur who got into online marketing, built a marketplace website, and just finished a book about online marketing that’ll appeal to programmers and other technical types. Now I want to recruit early readers to review it (good or bad–as your please) on Amazon. Any takers (non-binding, of course), contact me here: https://www.jackkinsella.ie/customer_support_requests/new Long Version: Six years ago, I programmed a web app, but it didn’t get much traffic, so I started researching everything on online marketing. I thought the best way to…
2016
- 21VF
Hey HN. We're Mus and Isaac - creators of LightLayer. We've been outputting a ton more code since using agentic dev tools. It's been great. But we're starting to see a new bottleneck emerge that's no longer writing the actual code: reviewing code. We’d love to hear from folks here if they’re feeling the inertia of code reviews a lot more these days with the surge in development velocity. For us, it was the reason we decided to pivot what we were working on before, and go full-time on building a workspace aimed at bringing the code review experience up to speed for the AI era. To be clear:…
2025 · lightlayer.dev
- 22
- 23CT
Hello folks! Me and a small group of developers started a free newsletter. The idea is to share 3 web dev tips every Monday. Our goal is to improve our writing skills and share knowledge as much as possible. So far, few hundreds of developers have subscribed and seem to like it. To get a feeling of what kind of stuff we share, here is an example of last Monday's issue: https://us4.campaign-archive.com/?u=5e499c75818d4611a008adfb5&id=106e5fbc71 If this is something that would interest you, you can subscribe here (its completely free):…
2019
- 24IT
I created http://devtest.net as a weekend project, and I'm pretty proud of it from a technical and UI standpoint. The problem is, I've built this by myself in a bit of a vacuum, to "scratch my own itch", and I don't know if this is useful to anyone other than me. I'm also not so hot on the business side and don't really know what I'm doing. Basically, I'm looking for some advice, now that I've actually launched, what now? One thing that this has shown me is that I'm capable of putting together a pretty decent web application on my own in my spare time. Should I stick with this idea, or…
2012
Ranked by how close each launch is in meaning, then by votes. Refine with a description →