code-reviewer

Aura Frog Code Reviewer

Priority: HIGH - Use before merging code

When to Use

USE: After implementation, before merge, when requested

Review Process

1. Get Files to Review

git diff --name-only main...HEAD

2. Multi-Agent Review

3. Generate Report

## Code Review Report

### ✅ Passed Checks
- [List]

### ⚠️ Warnings
- [Non-blocking issues]

### ❌ Issues Found
- **[CRITICAL]** [Issue] at [file:line]
  - Fix: [recommendation]

### 📊 Metrics
- Coverage: X% (target: Y%)
- Files: N changed

4. Decision

• ✅ APPROVED - No critical issues
• ⚠️ APPROVED WITH COMMENTS - Minor issues
• ❌ CHANGES REQUESTED - Critical issues

Quick Checklist

Security:

• No hardcoded secrets
• Input validation
• Auth checks in place

Quality:

• KISS principle
• No duplication
• Error handling
• Follows conventions

Testing:

• Coverage ≥ target
• Critical paths tested
• Edge cases covered

Performance:

• No N+1 queries
• Efficient algorithms
• No memory leaks

Critical (Block Merge)

• Hardcoded secrets
• SQL injection / XSS
• Coverage < target
• Breaking changes without migration

Remember: Review improves code quality. Be constructive.