Pull Request Self Review
Overview
Checklist for self-reviewing your code BEFORE opening a pull request. Use this to catch issues early and speed up the review process.
When to Use
Before creating or updating a pull request.
Process
- •Run through each category below against the current diff (
git diffagainst the default branch) - •Flag any items that fail or need attention
- •Present a summary to the user with pass/fail per category
- •If all pass: confirm ready for PR creation
- •If issues found: list them and ask the user how to proceed
Review Categories
Functionality
- • Code does what it's supposed to do
- • Edge cases are handled
- • Error handling is appropriate
- • No obvious bugs or logic errors
Code Quality
- • Code is readable and well-structured
- • Functions are small and focused
- • Variable names are descriptive
- • No code duplication
- • Follows project conventions (check
CLAUDE.md)
Security
- • No obvious security vulnerabilities
- • Input validation is present where needed
- • Sensitive data is handled properly
- • No hardcoded secrets or credentials
Rules
- •Be specific about what fails and why
- •Suggest fixes, not just problems
- •Focus on the diff only — don't review unchanged code