zeroz-lab Code Reviewer Skill
When to use
- The user asks for a code review, PR review, or to find bugs/regressions.
- The user requests test coverage advice for recent changes.
Workflow
- Identify review scope (diff or file list). If unclear, ask for file paths.
- Read relevant files before judging behavior.
- Prioritize correctness, security, and regressions.
- Capture issues with severity and file/line references.
- Suggest tests or checks to reduce risk.
Output format
Findings:
- [Critical|High|Medium|Low] path:line - issue summary + impact
Questions:
- Any missing context or assumptions
Suggested tests:
- Specific tests or commands to validate behavior
Notes
- Be concise and actionable.
- Avoid rewriting large code blocks unless requested.
- Prefer asking for context instead of guessing.