alt Hacker NewsMy team uses draft PRs and goes through a process, including AI review, before removing the draft status thereby triggering any remaining human review.
A PR is also a decent UI for getting the feedback but especially so for documenting/discussing the AI review suggestions with the team, just like human review.
AI review is also not equivalent to linter and static checks. It can suggest practices appropriate for the language and appropriate for your code base. Like a lot of my AI experiences it's pretty hit or miss and it's non-deterministic but it doesn't have much cost to disregard the misses and I appreciate the hits.
I'm starting to repeat myself here: If you need/want the opinion of an AI on the changes you make, you should run the robot locally BEFORE you make a pr. I would even say: before you even push commits to the central repository.