| name | code-review-checklist |
| description | Review code changes for correctness, security, performance, and maintainability. Use for PR reviews,
code audits, pre-merge checks, or quality validation of Laravel + React code. EXCLUSIVE to reviewer agent.
|
| allowed-tools | Read, Grep, Glob, Bash |
Code Review Checklist
Exclusive to: reviewer agent
Validation Loop (MANDATORY)
Before completing any review, verify the codebase passes all checks:
composer test # All PHP tests pass
npm run types # No TypeScript errors
npm run lint # No linting errors
./vendor/bin/pint --test # PHP style OK
Report any failures as Critical findings.
Instructions
- Review against project standards in
docs/code-standards.md
- Run through the checklist below
- Report issues by severity (Critical โ Warning โ Suggestion)
Review Checklist
โ
Correctness
๐ Security (OWASP)
โก Performance
๐งน Maintainability
๐จ Frontend
๐ Documentation
Laravel Security Checks
| Check |
Verify |
| Mass assignment |
$fillable or $guarded defined |
| Authorization |
Policy or Gate used |
| Validation |
FormRequest with rules |
| CSRF |
@csrf in forms |
| SQL injection |
No raw queries with user input |
React Security Checks
| Check |
Verify |
| XSS |
No dangerouslySetInnerHTML |
| Props |
TypeScript interfaces used |
| Secrets |
No sensitive data in client |
Severity Guide
| Level |
Criteria |
Action |
| ๐จ Critical |
Security flaw, data loss, breaks functionality |
Block merge |
| โ ๏ธ Warning |
Performance issue, code smell, missing test |
Request fix |
| ๐ก Suggestion |
Style improvement, better pattern |
Optional |
Output Format
## ๐ Review Summary
[One paragraph overview]
## ๐จ Critical (must fix)
1. [Issue]: [File:Line] โ [Why critical]
## โ ๏ธ Warnings (should fix)
1. [Issue]: [File:Line] โ [Recommendation]
## ๐ก Suggestions (nice to have)
1. [Suggestion]: [File:Line] โ [Improvement]
## โ
What's Good
- [Positive observation]
Examples
- "Review this PR before merge"
- "Check this code for security issues"
- "Audit changes for performance"