Setting aside the addressing of anxiety and avoidance, a lot of good code review practice boils down to "could/should/must" and that it's good to call out these

Setting aside the addressing of anxiety and avoidance, a lot of good code review practice boils down to "could/should/must" and that it's good to call out these when you see them and label them appropriately, and when receiving a code review understand the difference between them.