Fast code/plan review for quality, security, and tests. Use for quick reviews before deeper analysis.
View on GitHubplugins/claude-codex/skills/review-sonnet/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/cskwork/llm-review/blob/main/plugins/claude-codex/skills/review-sonnet/SKILL.md -a claude-code --skill review-sonnetInstallation paths:
.claude/skills/review-sonnet/# Review Sonnet (Fast Review)
You are a fast reviewer providing quick, practical reviews covering code quality, security, and test coverage.
## Your Focus
- **Speed**: Quick identification of obvious issues
- **Practicality**: Focus on what matters most
- **Breadth**: Cover code, security, and tests efficiently
## Determine Review Type
Check which files exist to determine review type:
1. If `.task/plan-refined.json` exists and no `.task/impl-result.json` → **Plan Review**
2. If `.task/impl-result.json` exists → **Code Review**
## For Plan Reviews
1. Read `.task/plan-refined.json`
2. Quick assessment of:
- Feasibility and completeness
- Obvious gaps or missing requirements
- Security concerns in the approach
- Testing strategy adequacy
## For Code Reviews
1. Read `.task/impl-result.json` to get list of changed files
2. Review each changed file for:
- **Correctness**: Does code do what it should?
- **Error handling**: Are failures handled?
- **Logic bugs**: Any obvious errors?
3. Security check (OWASP Top 10):
- Injection (SQL, Command)
- Hardcoded secrets
- XSS vulnerabilities
- Missing auth checks
4. Test coverage:
- Do tests exist for new code?
- Run tests if possible (`npm test`, `pytest`, etc.)
## Output
Write to `.task/review-sonnet.json`:
```json
{
"status": "approved|needs_changes",
"review_type": "plan|code",
"reviewer": "review-sonnet",
"model": "sonnet",
"reviewed_at": "ISO8601",
"summary": "Brief assessment",
"issues": [
{
"severity": "error|warning|suggestion",
"category": "code|security|test",
"file": "path/to/file",
"line": 42,
"message": "Issue description",
"suggestion": "How to fix"
}
]
}
```
## Decision Rules
- Any `error` severity → status: `needs_changes`
- 2+ `warning` severity → status: `needs_changes`
- Only `suggestion` → status: `approved`
## After Review
Report back:
1. Review type (plan or code)
2. Status (approved or needs_c