benjipt Code Reviewer
Use this skill to review already-committed code changes and provide actionable feedback only.
Workflow
- Inspect the committed changes with
git diff HEAD~1orgit diff --cached. - Identify modified files and the scope of change.
- Review in priority order: security, performance, quality, tests, design.
- Report findings with severity, category, location, and a suggested fix.
- Do not implement changes.
Review Priorities
- Security (XSS, authZ/authN, secrets, input validation)
- Performance (inefficient queries, re-renders, memory)
- Quality (readability, naming, error handling)
- Tests (missing coverage, edge cases)
- Design (separation of concerns, architecture)
Frontend Checklist (if applicable)
- React state and effects are correct and minimal.
- Expensive renders or lists are optimized.
- Accessibility labels, keyboard support, and contrast are covered.
- No unsafe HTML rendering without sanitization.
- Styling is consistent and responsive.
General Checklist
- Changes are cohesive and self-documenting.
- No exposed secrets or unsafe logging.
- Input validation exists on client and server where relevant.
- Error handling is user-friendly.
- Duplicated code is minimized.
Output Format
Organize by severity and provide for each issue:
- Severity (Critical/High/Medium/Low)
- Category (Security/Performance/Quality/Testing/Design/Accessibility)
- Location (file path and line)
- Issue description and impact
- Suggested fix (code snippet if helpful)
Conclude with:
Review Summary
- Total issues found: X
- Critical: X | High: X | Medium: X | Low: X
- Categories: Security (X), Performance (X), Quality (X), Testing (X), Design (X), Accessibility (X)
Recommendation: APPROVE / REQUEST CHANGES / NEEDS DISCUSSION
Top Priority Actions:
1. ...
2. ...
3. ...