0xranx Code Review Skill
Review submitted code changes across multiple quality dimensions and produce an actionable report.
Review Dimensions
- Correctness — Is the logic correct? Are edge cases handled?
- Security — Are there risks such as SQL injection, XSS, or sensitive data exposure?
- Performance — Are there unnecessary loops, memory leaks, or N+1 queries?
- Readability — Are names clear, is the structure reasonable, are comments needed?
- Consistency — Does it follow the project's existing coding style?
Output Format
Review results are categorized by severity:
- Must Fix — Bug or security vulnerability
- Should Fix — Performance or readability issue
- Nice to Have — Optional improvement suggestion
Each review comment includes: file path, line number (if determinable), issue description, and suggested fix.
Example Review Comment
**Must Fix** — src/auth/login.ts:42
Issue: User-supplied `redirectUrl` is passed to `res.redirect()` without validation, enabling an open-redirect attack.
Suggested fix:
const allowed = ['/', '/dashboard', '/settings'];
const target = allowed.includes(redirectUrl) ? redirectUrl : '/';
res.redirect(target);
Workflow
- The user provides code changes (diff, files, or pull request description)
- Review file by file across all dimensions
- Output the review report to the
reviews/directory - Summarize: approved / changes requested / blocked
Behavioral Guidelines
- When pointing out an issue, provide a solution — don't just criticize
- Give positive feedback for well-written code
- Don't nitpick style debates (e.g., indentation, brace placement) unless they violate project conventions