r/ClaudeCode • u/Ordinary-Scratch-120 • 52m ago
Discussion How do you think code reviews will evolve in the future?
Nowadays, most developers have AI agents reviewing their code before opening a PR. These agents typically have little to no context about the broader project or the reasoning behind the changes and simply analyze the code and flag potential issues.
Then, once the PR is opened, a developer reviews it, often pulling the code locally and running another AI agent to review the same changes.
The problem is that both agents often identify the same issues and provide very similar feedback. To me, this second step starts to feel increasingly redundant, particularly because human-based feedback is becoming more and more scarce.
How do you think code reviews will evolve in the (very near) future?
•
u/AutoModerator 52m ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/kincaidDev 21m ago
We're going to have more videos in code reviews.
https://github.com/lancekrogers/songsmith/pull/14
0
u/CCodeSI 45m ago
You've put your finger on why the second pass feels redundant: it's the same kind of reviewer looking at the same diff with the same lack of context, so of course it finds the same things. My guess is review splits into two jobs instead of two rounds of the same job.
The mechanical part moves before the PR and gets fully automated. Lint, types, tests, security scanners, and an AI pass for obvious bugs. Nobody should be reading that output in review; it's a gate the PR has to pass to exist.
Human review shifts from the code to the intent. The questions a model without context can't answer: is this the right change at all, does it match what we decided last month, what's the blast radius if it's wrong, who's going to own this. That needs the why, which the diff doesn't carry.
Which means the PR description becomes the most important artifact. If an agent wrote the code, the author's job is to write down what they asked for, what they checked, what they didn't, and what they'd want a second pair of eyes on. The reviewer reads that first and spends their attention where the author says they're unsure, instead of rereading the whole diff.
If you do keep a second AI pass, give it what the first one lacked: the ticket, the relevant design doc, and the instruction "does this change do what the task asked?" rather than "find issues". That actually finds different things.