Original link: How to Effective Code Review / LinkedIn / Rocky Bhatia.
The text is the same trivial text thatr exist thousands of places.
The interesting part is the pyramid. I think it illustrates a good point.
What is important is: the API developers will have to live with for 10-20-30-40 years, that the logic in the code actually works and that there is documentation so the code can be maintained. Verifying that test coverage is good and that all test pass and that the code is following company coding convention is something trivial that shoudl be automated.