Review Pull Request

Evaluate PR quality and provide structured feedback.

When to Use

Reviewing a PR before merge
Evaluating code quality and standards
Checking CI status and test coverage
Providing feedback to contributors

Quick Reference

# View PR details
gh pr view <pr>

# Check diff
gh pr diff <pr> | less

# View CI status
gh pr checks <pr>

# See review comments
gh api repos/OWNER/REPO/pulls/PR/comments

Review Checklist

[ ] Code follows project standards (CLAUDE.md)
[ ] All CI checks passing
[ ] Tests are present and passing
[ ] PR is linked to issue
[ ] Commit messages follow conventional commits
[ ] No security vulnerabilities
[ ] Documentation updated if needed
[ ] No unintended files included

Workflow

Get PR info: gh pr view <pr>
Review diff: gh pr diff <pr>
Check CI: gh pr checks <pr>
Analyze code: Focus on quality, standards, tests
Assess security: Look for vulnerabilities
Verify docs: Check if documentation updated
Provide feedback: Comment with findings

Review Focus Areas

Code Quality:

Clean, readable, maintainable
Follows CLAUDE.md guidelines
Proper error handling
No code duplication

Testing:

Tests present for new code
Tests passing
Adequate coverage
Edge cases covered

Documentation:

API documentation updated
Complex logic explained
README updated if needed
Examples provided if applicable

Standards Compliance:

Mojo syntax correct (for Mojo code)
No warnings or unused variables
Proper formatting
Conventional commit messages

Output Format

Provide review with sections:

Summary - Overall assessment
Strengths - What's done well
Issues - Problems that must be fixed
Suggestions - Optional improvements
Verdict - Approve / Request Changes / Comment

Error Handling

| Problem | Solution | |---------|----------| | PR not found | Verify PR number | | Auth failure | Check gh auth status | | CI pending | Note review based on current state |

References

See CLAUDE.md for project standards
See CLAUDE.md for Mojo syntax requirements
See CLAUDE.md for zero-warnings policy