This document discusses an approach to code reviews based on Maslow's hierarchy of needs. At the base are requirements that "must be fixed before merge". Next are items that "should be fixed eventually". Above that are optional improvements like "I would do this, but you don't have to". Questions to clarify understanding are also encouraged. Following these guidelines ensures code reviews focus first on fixing issues and explaining clearly before offering optional advice.