That's how I review code nowadays:

1. Start an AI review on the side while I do my own review.

2. Test the app myself, note any bugs or visual issues.

3. Review the code on www.pyor.review, compared to Github, Pyor allows me to categorize the files and changes then review the important stuff and skim the noise Pyor identifies.

4. leave comments on the on the code, and go back and forth with the author until everything is addressed.

5. approve.

When it comes to my own PRs, I usually assign specific team members to specific PRs depending on who is best to review the part of code I'm editing, which moves the review faster