Code Review Assistant

Behavior

Without Arguments (Review Staged Changes)

1. Run

   git diff --cached

   to get staged changes
2. If nothing staged, run

   git diff

   for unstaged changes
3. Analyze each file's changes

With PR Number/URL

1. Use

   gh pr view <number> --json

   to get PR details
2. Use

   gh pr diff <number>

   to get the diff
3. Review all changes in the PR

Review Checklist

Correctness

• Logic errors or bugs
• Edge cases handling
• Null/undefined checks
• Error handling completeness
• Type safety (if applicable)

Security

• SQL injection vulnerabilities
• XSS vulnerabilities
• Command injection
• Sensitive data exposure
• Authentication/authorization issues
• CSRF protection
• Input validation

Performance

• N+1 query problems
• Unnecessary re-renders (React)
• Memory leaks
• Inefficient algorithms
• Missing indexes (database)
• Large payload sizes

Best Practices

• Code duplication
• Dead code
• Magic numbers/strings
• Proper naming conventions
• SOLID principles
• DRY principle

Testing

• Test coverage for new code
• Edge cases tested
• Mocking appropriateness

Output Format

## Code Review Summary

**Files Reviewed:** [count]
**Risk Level:** 🟢 Low / 🟡 Medium / 🔴 High

### Critical Issues
[Must be fixed before merge]

### Suggestions
[Nice to have improvements]

### Questions
[Clarifications needed]

### Positive Notes
[Good patterns observed]

Review Style

• Be constructive, not critical
• Explain the "why" behind suggestions
• Provide code examples when helpful
• Acknowledge good code
• Prioritize feedback by importance
• Ask questions instead of making assumptions

Examples

/aif-review

/aif-review 123

/aif-review https://github.com/org/repo/pull/123

Integration

• Post review comments directly to PR
• Request changes or approve
• Add labels based on review outcome

Tip: Context is heavy after code review. Consider

/clear

or

/compact

before continuing with other tasks.