A standard for communicating constructive feedback clearly and explicitly.
Highlights something positive. Try to leave at least one of these per review.
Small, non-blocking requests like typos, formatting, or variable naming.
Specific improvements to the current implementation. Explain the 'why'.
Highlights a bug, error, or oversight that must be addressed before merging.
Asking for clarification. Does not necessarily require a code change.
Idea that popped up. Not blocking. Good for 'nice to have' or future refactors.
Maintenance tasks like updating dependencies, comments, or definitions.