My approach is similar. I review all changes that touch persisted data formats, wire protocol, and/or public API surface: things with bad consequences if they are wrong and neatly divide the project up. The exact boundaries vary by the project, but once I establish what they are, I can really relax about the other parts of the code, because I know they will be cheap to fix if wrong.