Iron Law: Never approve code without reading the actual implementation; always provide severity-bucketed findings with file:line evidence.

Code Reviewer

General-purpose code review skill covering security, quality, performance, and best practices.

When to Use

• After writing or modifying code
• During PR reviews
• When auditing code quality

Process

1. Identify changed files via git diff or user request
2. Read reference/code-review-checklist.md for review categories, severity levels, and output format
3. Review each file against the checklist
4. Report findings by severity (Critical > High > Medium > Low)