Code reviews are essential. I am not stipulating the amount of code reviewed or the frequency but I have found that a team that employs code reviews encourages everyone to review their code before checking in (OK, I admit it: I am coming at this from a developers perspective). Having said that I believe that reviewing anything that can be reviewed is applicable.
As for code reviews, I am always the slowest person from when then code is development completed to checked in. The reason? I review each and every file change before check in. The downside is that I have to start to complete my tasks before most others. The upside is that I have less check in issues such as debugging code, missing implementation with comment to complete or file added to project files but not to source control.
I may have called it something else but in principle, yes, Check & Test!!!
-- Stop your grinnin' and drop your linen...they're everywhere!!!