Ask HN: What are some things to put on a design or code review checklist?

I'm currently exploring the option for the other engineers on my team to implement a simple system of checklists to enforce best practices in code review and design (code design or "code architecture").

The goal with these checklists is to create a system in which everyone can check their code design against a checklist of best practices, considerations, and common pitfalls.

This would also help our small team with having a history of each person's checklist, and the discussion we started when reviewing their code & checklist.

Curious if anyone has implemented a checklist system in their engineering team, and if so, what some good items to put on the checklist are.