Since you specifically ask for e-books in your update, I'll point out that my company, SmartBear, gives away a book on code review. Unfortunately, it looks like you're in India which is not one of the countries we currently ship to. However, you'll be happy to note that the signup page linked above, includes links to several sample chapters from the book.
Our general recommendation on building code review checklists, is to spend time analyzing the bugs that you write. You need to go deeper than the individual cases and think about the underlying causes or classes of bugs.
Beyond the empirical data, there are some things that are necessarily bugs, but should be verified in code review to ensure maintainability of the software:
- Are there sufficient unit tests?
- Are classes and methods sufficiently and clearly documented?
- Are classes and method appropriately scoped?
Finally, if your organization is just adopting code reviews, start slow and be patient.