Paul Andrew shares with us a script which is useful for peer reviewing code before check-in:
Does the code include good comments? Things that explain the reason why logic has been implemented to assist future developers looking at the same code.
All to often I see code comments written that just translate from code to English and tell me what is happening. What should be fairly obvious to the reviewer as they read the code. Why is so much more important.
It’s a 20-point checklist, but worth reviewing and adapting for your own purposes.