Checklist before a PR review

• I haven’t committed unintentional artifacts (files, console logs, commented out code, etc.)
• PR highly focused
• Gotchas are documented in PR description, issues created etc.
• Descriptive naming
• Necessary tests are added
• PR feels lightweight to review
• At least this template is filled out

  # Description
  <!-- Issue number or link to the issue -->
  
  Resolves #123.
  
  links to design, preview, docs, etc.
  
  ## Notes/Screenshots/Videos
  
  Warnings, caveats, things to look at, etc
  
  ## To test
  
  - [ ] Do this
  - [ ] Do that
  - [ ] Check if works as expected

Read more

• Great read about code reviews by Michael Lynch to revisit from time to time