---
title: Code Review Checklist
---

:::caution[Programme Sunset]
The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.

I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.

Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
:::

**SELF-REVIEW CHECKLIST FOR CODE QUALITY**

Use this checklist to review your own code before merging pull requests or when preparing for optional code reviews.

## Code Quality

- [ ] Code follows project style guide and conventions
- [ ] Code is readable and well-organised
- [ ] Variable and function names are clear and descriptive
- [ ] Code is properly commented where necessary
- [ ] No commented-out code or debugging statements left in
- [ ] Code follows DRY (Don't Repeat Yourself) principles
- [ ] Functions and methods are appropriately sized and focused

## Functionality

- [ ] Code implements the intended feature correctly
- [ ] Edge cases are handled appropriately
- [ ] Error handling is implemented where needed
- [ ] User input is validated and sanitized
- [ ] Code handles null/undefined values appropriately

## Testing

- [ ] Unit tests are written and passing
- [ ] Integration tests are written and passing (if applicable)
- [ ] Test coverage is adequate for new functionality
- [ ] Tests are meaningful and test actual behavior
- [ ] All tests pass before submitting

## Security

- [ ] No sensitive data is hardcoded or exposed
- [ ] Authentication and authorization are properly implemented (if applicable)
- [ ] Input validation prevents injection attacks
- [ ] Dependencies are up to date and secure
- [ ] Security best practices are followed

## Performance

- [ ] Code performs efficiently
- [ ] No obvious performance bottlenecks
- [ ] Database queries are optimized (if applicable)
- [ ] Unnecessary computations are avoided

## Documentation

- [ ] Code is self-documenting with clear naming
- [ ] Complex logic is explained with comments
- [ ] README is updated if needed
- [ ] API documentation is updated if applicable

## Git Practices

- [ ] Commit messages are clear and descriptive
- [ ] Commits are appropriately sized
- [ ] Branch name follows naming conventions
- [ ] Pull request description explains changes clearly
- [ ] Related issues are linked in PR description

## Accessibility (if applicable)

- [ ] UI components are accessible
- [ ] ARIA labels are used where appropriate
- [ ] Keyboard navigation works
- [ ] Screen reader compatibility is considered

## Browser/Platform Compatibility (if applicable)

- [ ] Code works across target browsers/platforms
- [ ] Responsive design is implemented (if applicable)
- [ ] Cross-browser testing is done (if applicable)

---

*This checklist is a starting point. Customize it based on your project's specific requirements and standards.*

