I get asked about code review checklists all the time. Mostly the question is: "Do you have a sample checklist we can use?"
Seems like a reasonable question... except there's no good answer! A checklist is unique to a team, a language, and a goal. A checklist changes over time as people get good at addressing the issues. A checklist has only a few items on it, not two pages of items.
The real question is: How do I build an appropriate checklist? Following up with: What are the common pitfalls to avoid? How do I keep the checklist updated?
Good questions! Glad you asked. The answer is in an article I wrote for CM Crossroads: Checklists: You Build me up Just to Knock me Down.
P.S. I know, in the book I gave some sample checklist items... I hope this doesn't make me a bad person.