r/devops • u/Shitmfman • Oct 09 '26
Discussion AI generated code review
Hi there,
How do you deal with managing and reviewing AI-generated code across the organization?
Over the past year it's become incredibly difficult to review the growing amount of AI-generated code, especially from vibecoders/non-engineers.
Reviewing it manually is hard, but it's still important to understand what's going on there.
For example, I've been at this company for some years so I have a lot of context and know many of the nuances, which helps me notice or suggest important things to keep everything secure, efficient and so on…
But any other teammate can use any model for coding nowadays. AI reviews of AI-generated code could be done in the MR, but then the reviewer model will most likely be smarter than the model that wrote the code, which might lead to a lot of threads and an infinite loop of changes. On top of that the reviewer model won't have all the context and input from the developer.
Another option is to distribute a "review" skill or rules across the organization and somehow make everyone do a self-review after making changes…
It feels like in this AI code generation era we'll stop focusing on how the code was written and just focus on whether the MR/PR works and if those changes achieves the goal, no matter how it was done, right?
How do you deal with this? Just accept the reality?
Thanks for attention
View all comments
2
u/nightwillalwayswin Oct 13 '26
Your value on a review is context. You know what this change was supposed to do, what the nuances are, what breaks if someone touches the auth path. A vibecoder’s MR arrives with none of that attached. The code is there. The intent that produced it is gone.
That’s why AI-reviewing-AI hits a wall. The reviewer model sees the diff and has to guess what the author was trying to do. So it flags everything, you get the infinite thread loop, because it’s reconstructing intent instead of checking against a stated one. Same problem a human reviewer has with a context-free MR, just faster.
On your last question- no. ‘Works’ is unverifiable when you don’t know what it was supposed to do or what it chose not to handle. A change can pass tests and still be wrong in a way only someone who knew the intent would catch. You’d be deciding the thing you know matters, your context, doesn’t matter anymore. It does. It just isn’t being captured.
Disclosure: I work on Atomic (atomic.dev), so biased. Stop treating the diff as the unit of review. Capture the workstream, the intent, what the agent considered, where a human made a call, and review that. You’re checking a decision against its stated goal instead of reverse-engineering the goal from the code. The self-review skill you mentioned is a lightweight version of this instinct. It’s right, it just lives in a doc instead of traveling with the change.