When conducting peer code reviews, fill out the template below in a comment on your peer’s pull request:
# Peer Code Review
## Summary (1-3 sentences)
Briefly describe what the pull request does and what the main changes/additions are.
---
## Correctness
Check the box for each requirement you can confirm is satisfied based on the PR and evidence (tests, screenshots, docs, output, etc.):
- [ ] Core functionality works as intended
- [ ] Handles edge cases and error conditions appropriately
### Evidence / Notes
- What evidence did you use to verify correctness (tests run, screenshots, sample output, reasoning from code)?
- If anything seems incorrect or incomplete, describe what you observed and where.
---
## Design
Choose one:
- [ ] Exemplary - Clean, modular, easy to follow. Strong separation of concerns. Minimal complexity.
- [ ] Satisfactory - Works well overall with minor complexity/redundancy or small opportunities to refactor.
- [ ] Needs Improvement - Hard to follow, overly complex, tightly coupled, or missing structure.
- [ ] Missing/None - Design is unclear or not reasonably maintainable.
### Explain your choice
- Are any functions/classes doing too much or too long?
- Is the logic modular and reusable where appropriate?
- Are responsibilities clearly separated?
- Are there confusing dependencies, duplication, or overly complex logic?
---
## Code Style
Choose one:
- [ ] Exemplary - Consistent formatting, clear naming, helpful comments, follows style guide.
- [ ] Satisfactory - Minor style inconsistencies, but overall readable.
- [ ] Needs Improvement - Naming/formatting/commenting issues reduce readability.
- [ ] Missing/None - No consistent style; readability is severely impacted.
### Explain your choice
- [ ] Variable/function/class names are descriptive and consistent
- [ ] Formatting/indentation is consistent
- [ ] Comments/docstrings clarify non-obvious logic
- [ ] Code follows project/course style guidelines
## Inline Comments
Did you add any inline comments in the Files Changed tab? (So that the author of the PR doesn’t miss your inline comment)
- [ ] Yes
- [ ] No