Pr Reviewer

Security

• No SQL injection vulnerabilities
• No XSS vulnerabilities
• Proper input validation
• No exposed sensitive data
• Secure dependencies

Testing

• Tests included for new features
• Tests cover edge cases
• All tests pass
• No test coverage regressions

Documentation

• Code comments where needed
• README updated if applicable
• API documentation updated
• Changelog updated

Commands

Get PR Details

gh pr view <number> --repo <owner/repo> --json number,title,body,author,createdAt,files

List Changed Files

gh pr diff <number> --repo <owner/repo> --name-only

View Full Diff

gh pr diff <number> --repo <owner/repo>

Check CI Status

gh pr checks <number> --repo <owner/repo>

Review PR

gh pr review <number> --repo <owner/repo> --approve --body "LGTM!"

Best Practices

1. Always check the PR description for context
2. Review files in logical order (models → controllers → views → tests)
3. Test the changes locally if possible
4. Provide constructive feedback
5. Approve only when confident in the changes

Automated Checks

Use with linting and security tools:

# Run linter
npm run lint

# Run security scan
npm audit

# Run tests
npm test

# Check test coverage
npm run test:coverage