- Does the reviewer need to know anything about the existing codebase/functionality to help them understand these changes?
- If the changes are complex, summarise them in a few sentences to help the reviewer understand the big picture.
- If the changes are confusing, explain why they are needed.
### Contents
- Give a high-level summary of what changes are included.
- If there are many changes, summarise the changes in each high-level folder.
### Areas to focus
- Do you have specific questions for the reviewer? (e.g. could I structure the code better in this specific file?)
- What are the highest risk/most complicated changes that the reviewer should focus on?
### Screenshots
- Would this code be easier to review if the reviewer could see the UI?