This is very much a marketing post, but this:

Most code review tools start and end with the diff. They might expand to the file, or even the repository. But that’s not how the best reviewers think.

When a senior engineer reviews code, they’re drawing on years of institutional knowledge. They remember that Slack thread from six months ago about why the team chose this particular database pattern. They know that David on the platform team has strong opinions about error handling. They’ve internalized dozens of unwritten conventions that never made it into any style guide or lint.

is very true (it brings Chesterton’s Fence to mind) and not something that comes up in a lot of code review discussions.