Code reviewer
Skill Claude-Code-Community-Ireland/claude-code-resources/skills/development/code-reviewer
Community-curated collection of Claude Code skills, agents, CLAUDE.md files, PRDs, prompts, and more. Run by Claude Code Community Ireland.From the repository description
npx -y skills add Claude-Code-Community-Ireland/claude-code-resources --skill code-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Code Review Skill
Perform thorough, constructive code reviews on pull requests and code changes.
Instructions
When reviewing code:
1. First Pass - Understanding
- Read the PR description and linked issues
- Understand the intent and context
- Identify the scope of changes
2. Check for Issues
Correctness
- Logic errors or bugs
- Edge cases not handled
- Race conditions or concurrency issues
- Null/undefined handling
Security
- Input validation
- SQL injection, XSS vulnerabilities
- Hardcoded secrets or credentials
- Proper authentication/authorization
Performance
- Unnecessary loops or computations
- N+1 queries
- Memory leaks
- Missing caching opportunities
Maintainability
- Code clarity and readability
- Proper naming conventions
- DRY principle violations
- Missing or unclear comments
Testing
- Test coverage for new code
- Edge cases tested
- Integration tests where needed
3. Provide Feedback
Use this format for each comment:
**[Category]** File:Line
Description of the issue or suggestion.
Suggested fix (if applicable):
\`\`\`
code example
\`\`\`
4. Summary
End with a summary:
- Overall assessment (Approve/Request Changes/Comment)
- Key strengths of the PR
- Critical issues that must be addressed
- Nice-to-have improvements
Tone Guidelines
- Be constructive, not critical
- Explain the "why" behind suggestions
- Acknowledge good practices
- Ask questions rather than make demands
- Offer to help if complex changes needed