Code reviews do not have to block checkins. See also "continuous integration". It's a way.
Nobody ever wants to do it, but I've used a statement of work approach in the past.
I once used the wrong version of coding standards in a shop, and heard about it in a performance review. I'm in no way convinced this was inadvertent. My piece had negative defects - I found a dozen or so old crufty bugs in my testing. The rest of the team took months getting integration right.