42 stories tagged code-review, newest first.
49 points by ericholiveira | 28 comments
GitHub repository for Farol, an open-source CLI and GitHub Action that scores pull request merge risk, highlighting risky files, reach, diff coverage and contract breaks.
20 points by tob_scott_a | 2 comments
A Trail of Bits blog post on reviewing changes made by AI coding agents, focusing on unintended modifications beyond the requested bug fix.
38 points by alexmolas | 22 comments
Will Larson describes Imprint's `small-change` process, which uses CI checks and AI review skills to fast-track approval of small, low-risk pull requests.
534 points by rzk | 650 comments
An Ask HN thread asking how engineers cope with shipping AI-generated code they don't fully understand, citing a Meta engineer's LinkedIn post.
407 points by pretext | 386 comments
An Anthropic engineering blog post by Addy Osmani describing how the Claude Code team reviews the high volume of code produced by AI agents while minimizing human review time.
303 points by gumby | 263 comments
Ars Technica article on a study finding AI coding agents increase code output but efficiency gains are absorbed by human code review bottlenecks.
11 points by bradleygibbs | 7 comments
Blog post by Bradley Gibbs on designing AI-assisted development loops to qualify generated code for human review, reduce wasted work, and measure verification value.
291 points by drogus | 128 comments
Blog post by Piotr Sarnacki critiquing DHH's AI-agent-generated rewrites of Campfire Once into Rust and other languages, arguing developers still need to read code and think.
10 points by handfuloflight | 4 comments
Landing page for Spinal, an upcoming low-latency tool for exploring codebases and their history, with a GitHub/email waitlist signup.
10 points by edmorley | 4 comments
A YouTube music video titled "LGTM (Looks Good to Me)" about AI coding agents and code review, labeled as AI-generated and credited to Claude Opus 5.5.
55 points by mwil1000 | 8 comments
GitHub repository for Diffle, a keyboard-first diff viewer with LSP support and GitHub integration for code and PR review.
3 points by pnezis | 0 comments
GitHub repository for Pinrail, an Apache-2.0 desktop app and CLI that queues coding agent work in an inbox for human review.
142 points by utiiiD | 88 comments
Adaptive Capacity Labs blog post arguing that code review involves more than defect detection that can be automated.
38 points by namanbhulawat | 39 comments
GitHub repository for jev-code-reviewer, an MIT-licensed tool that prioritizes code changes for human review and uses OpenAI to explain them, via CLI, agent skill, and GitHub extension.
5 points by snyy | 1 comments
Landing page for Critic, a code review platform where AI agents annotate their changes and reviewers can chat with the agent that wrote the code.
395 points by sidharthkmenon | 129 comments
GitHub repository for Whiteboard, an MIT-licensed desktop IDE built on Code-OSS where developers and AI agents collaborate on software design via diagrams and diffs.
311 points by dimonomid | 438 comments
Blog post by Alexandru Nedelcu arguing that AI lacks wisdom and that relying on it for coding, skipping code reviews and reading code, erodes developers' own judgment.
642 points by khy | 234 comments
Zed blog post by Nathan Sobo announcing Delta, a multiplayer environment for coding with AI agents and reviewing their work, now in private beta.
877 points by florianherrengt | 785 comments
Blog post arguing that AI-generated code floods senior engineers with huge PRs and is hollowing out the middle tier of software engineering roles.
1668 points by ngruhn | 676 comments
A blog post asking people not to paste verbatim AI chatbot responses into Slack, pull request reviews, or group chats, arguing it adds effort rather than value.
754 points by tomzorz | 266 comments
GitHub changelog post announcing that stacked pull requests, which can be merged together as a stack, are now in public preview.
560 points by backlit4034 | 431 comments
Personal blog post by a software engineer explaining why he stopped arguing with people over technical correctness and what he learned about arguments.
1613 points by jjfoooo4 | 477 comments
Blog post arguing that people forwarding AI-generated text to colleagues should first digest it and demonstrate their own effort before asking for others' attention.
1102 points by signa11 | 407 comments
Blog post by Nolan Lawson arguing that LLMs can be used to write higher-quality code more slowly, such as finding bugs, rather than producing low-quality code fast.
343 points by BOOSTERHIDROGEN | 168 comments
Addy Osmani's blog post introducing Agent Skills, an attempt to make AI coding agents follow senior-engineer practices like specs, tests, reviews, and scope discipline.
405 points by pella | 234 comments
Blog post describing the 'over-editing' problem, where AI coding models rewrite more code than needed when fixing simple bugs, with accompanying code.
847 points by ezekg | 475 comments
Documentation landing page for GitHub Stacked PRs, a private-preview feature and gh stack CLI for splitting large changes into small, dependent pull requests.
2140 points by grepsedawk | 459 comments
Blog post by Ally Piechowski describing five git commands to find churn hotspots, bus factor, bug clusters, and crisis patterns before reading a codebase.
456 points by greyface- | 272 comments
Blog post on apenwarr arguing that each added layer of review in an organization slows work down by roughly an order of magnitude.
395 points by aray07 | 446 comments
Blog post by Abhishek Ray about running autonomous coding agents overnight and the problem of verifying the quality of the code they ship.
545 points by ndr42 | 435 comments
Ars Technica article (via Financial Times) reporting Amazon will require senior engineers to approve AI-assisted code changes after AWS outages linked to AI tools.
777 points by simonw | 599 comments
Simon Willison blog post arguing developers must prove their code works through manual and automated testing before submitting it, especially when using LLM tools.
349 points by sealeck | 203 comments
TigerBeetle blog post by matklad arguing that code review workflows, such as GitHub pull requests, can be improved.
541 points by antirez | 365 comments
Blog post by antirez (Redis creator) giving an update on how he uses frontier LLMs like Gemini 2.5 Pro and Claude for programming in summer 2025.
626 points by phire | 309 comments
Blog post arguing that writing code was never the bottleneck in software engineering; reviews, knowledge transfer, testing, and coordination are.
573 points by ecz | 431 comments
Cursor's changelog entry for version 1.0, introducing BugBot code review, memories, one-click MCP install, Jupyter support, and general availability of Background Agent.
339 points by ulrischa | 264 comments
Simon Willison blog post arguing that LLM hallucinations in code are the least harmful kind of mistake because running the code exposes them immediately.
417 points by namanyayg | 215 comments
A blog post describing an experiment in getting AI to analyze codebases the way a senior developer reads code, prompted by failures on a React codebase.
443 points by prathameshgh | 272 comments
Ask HN post from a new-graduate data engineer acting as tech lead at a non-tech oil company, asking how to grow without senior engineers to learn from.
597 points by Ameo | 150 comments
A blog post recounting the author's experience fixing a bug in Chromium/Google Chrome as a first-time contributor, from building the code to code review and release.
597 points by panqueca | 645 comments
An Ask HN thread where the poster describes automating a deprecated internal tool and asks others about the most useless projects they have worked on.
545 points by molly0 | 565 comments
Ask HN thread where a developer asks how to avoid taking constructive criticism of their work, such as PR comments, personally.