Depends what do you look for in code review? I only check the code architecture.
Does it use dependency injection as we set it up?
Are domain/data/presentation classes in correct modules?
Is the data flow hierarchy correct according to clean arch?
Are unit tests written, is the code coverage better or at least the same?
Are classes doing specific things named according to patterns how we name them?
Is everything generally following the same pattern as the rest of the project?
Code is mostly about patterns, and if you know the pattern, making sure the AI agent follows it gives you the peace of mind that you can also manually check and understand it later. Everything else is a fine detail, and at the moment, this is something that I don't think is that important unless you have specific bottlenecks or issues, which again... you fix with a new prompt...
First articulate the purpose of code reviews (typically, there are about 3 or 4).
Then think about whether there are other, better ways, to accomplish those goals, assuming you still want to reach those goals. That can inform how you modify your SDLC.
Go all in on AI, stop worrying about quality. When shit breaks, spin a replica and have an agent look at the logs and figure it out while hoping the replica restores service. It might sound counter-intuitive, but you know who's doing it? Your competition.
It's cheaper to create than it is to understand, so if you have no understanding in your SDLC, you can't expect to have it on incidents.
What @pluc said basically. You could use stuff like https://bte.mills.io and https://git.mills.io/prologic/squint to help test/validate the "behaviour" of what is being developed/built. Try to think of yourself as the "Product Designer" and "Product Owner". Worry less about the _actual_ code itself, and more about how the software/product behaves. Write specifications that can be validated and ask yoru favourite coding assistant to ensure that those are validated.
Does it use dependency injection as we set it up? Are domain/data/presentation classes in correct modules? Is the data flow hierarchy correct according to clean arch? Are unit tests written, is the code coverage better or at least the same? Are classes doing specific things named according to patterns how we name them? Is everything generally following the same pattern as the rest of the project?
Code is mostly about patterns, and if you know the pattern, making sure the AI agent follows it gives you the peace of mind that you can also manually check and understand it later. Everything else is a fine detail, and at the moment, this is something that I don't think is that important unless you have specific bottlenecks or issues, which again... you fix with a new prompt...
Then think about whether there are other, better ways, to accomplish those goals, assuming you still want to reach those goals. That can inform how you modify your SDLC.
It's cheaper to create than it is to understand, so if you have no understanding in your SDLC, you can't expect to have it on incidents.