Autonomous code review for best practices, security, performance, and potential issues. Runs in isolation with read-only tools using Opus model. Use when reviewing code, checking PRs, or analysing code quality.
Pro scans all 2 files and shows the line behind each finding
Scanned 9/27/2026
npx -y skills add David-Li0406/meta-skill-evloving --skill code-reviewer-22 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Code Reviewer 22?
Add the live security badge to your README β it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/david-li0406-code-reviewer-22)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: code-reviewer
description: Autonomous code review for best practices, security, performance, and potential issues. Runs in isolation with read-only tools using Opus model. Use when reviewing code, checking PRs, or analysing code quality.
context: agent
skills: bugmagnet
---
# Code Reviewer
Autonomous code review agent that analyses code for best practices, security, performance, and potential issues.
## When to Use
- After completing a feature (before merging)
- When reviewing pull requests
- When asked to critique or analyse implementation
- As part of quality gates in the XP workflow
## What It Does
1. Determines review scope (diff, file, or directory)
2. Reads target files
3. Searches for related patterns using Grep/Glob
4. Applies checklist criteria
5. Runs bugmagnet for test coverage gaps
6. Returns structured findings report
## Output Severity Levels
- π΄ **CRITICAL:** Must fix before merge
- π‘ **WARNING:** Should address
- βΉοΈ **SUGGESTION:** Nice to have
## Checklist Categories
### Code Organisation & Structure
- Single Responsibility Principle
- Appropriate abstraction levels
- Clear naming conventions
- Duplication identified
### Functional Programming
- Pure functions where possible
- Side effects explicit and contained
- Immutable data preferred
- No early returns
### Error Handling
- All error cases handled
- Appropriate error types
- No silent failures
### Performance
- No obvious inefficiencies
- Appropriate data structures
- Resource clean-up
### Security
- Input validation present
- No hardcoded secrets
- Injection prevention
### Test Coverage
- All code paths tested
- Edge cases covered
- Behaviour-focused tests
## Agent Properties
- **Model:** Opus (for thorough analysis)
- **Tools:** Read, Grep, Glob, Bash (read-only)
- **Skills:** bugmagnet (for test gap analysis)
- **Isolation:** Runs in separate context
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!