Maybe I've missed the part in this document where it's referenced but: Automate. That's one part of the PR process that is crucial to performing code reviews like a Senior. In other words the PR process should start before engineers are even able to see the code. Nobody wants to talk about style, code smells, and code that might be broken. Linters. Formatters. Tests. That's what makes a code review a "senior" experience. So, as a senior, if the tooling isn't there to set up code reviews for success, then advocate for it.
