# Review instructions

## What Important means here

Reserve Important for findings that would break behavior, use incorrect logic, or introduce a design flaw
that will derail future development. We want the code to speak for itself. High quality readable code tells
the story. It does not need comments to explain what is happening. Comments should primarily tell the why, the code will tell the
what and how.

## Why we care about Nits

Nits identify weaknesses in the code structure, style, and naming. Consistent, digestible code is critical to the long term
health of the repository. We do not want to make sacrifices with readability in this repo. We want it to be clear for new
developers what structure they should follow by looking at the existing code, not having to rely on inside knowledge,
extensive documentation, and excessive comments. There is no cap on the number of Nits, and all Nits must be resolved before
approving the PR.

## Always check

- Code comes with unit tests where possible