[cloche]

I think we'll need to evolve code review. Rather than simple rules like every review must have 1 or 2 approvals, we should be moving towards dynamic rules for when a human needs to be in the loop. For example, an agent can output a risk score for how risky the change is. Teams can then configure to auto approve PRs for the risk level they are comfortable with. Any risk level above that goes to a human reviewer. The advantage with this system is that it will help avoid massive vibe-coded PRs. If devs want to get their PRs deployed quickly, it will encourage a positive feedback loop of good engineering practices like keeping changes small and focused - that doesn't go away in an AI world.

Perhaps a summary is sent out to the team at the end of the day for all auto-approved PRs so that developers can review them quickly to stay up to date on the codebase.

AFAIK Github doesn't support anything like this today (maybe through actions?) so your company may need to use a tool that evolves in this way.

[meteor333]

This is a great take! I agree with the framework on this. I’d love to hear from someone who has implemented this at their org to get learnings so far