Automated Code Review
You are performing an automated code review for the project at $ARGUMENTS.
Focus Areas
- Security: Check for vulnerabilities, injection risks, exposed secrets
- Performance: Identify inefficient code, N+1 queries, memory leaks
- Maintainability: Code clarity, complexity, proper abstractions
- Best Practices: Language idioms, design patterns, testing
Dynamic Context
- Recent changes: !
git diff HEAD~5 --stat 2>/dev/null || echo "No recent changes"
- Current branch: !
git branch --show-current 2>/dev/null || echo "unknown"
- Uncommitted changes: !
git status --short 2>/dev/null || echo "Not a git repo"
Instructions
Gather Context
- Check
git status for current state
- Review
git diff for recent changes
- Identify the most modified files
Analyze Code
- Focus on files with recent changes
- Check for security issues (hardcoded secrets, SQL injection, XSS)
- Look for performance problems
- Evaluate code organization and readability
Provide Feedback
- Be specific with file paths and line numbers
- Explain why something is an issue
- Suggest concrete fixes
- Rate severity: low | medium | high | critical
Output Format
Return a JSON report:
{
"summary": "Brief overview of code health",
"files_reviewed": ["list of files"],
"issues": [
{
"file": "path/to/file.py",
"line": 42,
"severity": "high",
"category": "security",
"description": "SQL query uses string concatenation",
"suggestion": "Use parameterized queries instead"
}
],
"recommendations": [
"General improvement suggestions"
],
"metrics": {
"total_issues": 5,
"critical": 0,
"high": 1,
"medium": 2,
"low": 2
}
}
For detailed report template, see templates/report.md.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: code-review-833description: Automated code review with focus on security, performance, and maintainability. Use when reviewing code changes, PRs, or performing scheduled audits. Use when this capability is needed.4---56# Automated Code Review78You are performing an automated code review for the project at `$ARGUMENTS`.910## Focus Areas11- **Security**: Check for vulnerabilities, injection risks, exposed secrets12- **Performance**: Identify inefficient code, N+1 queries, memory leaks13- **Maintainability**: Code clarity, complexity, proper abstractions14- **Best Practices**: Language idioms, design patterns, testing1516## Dynamic Context17- Recent changes: !`git diff HEAD~5 --stat 2>/dev/null || echo "No recent changes"`18- Current branch: !`git branch --show-current 2>/dev/null || echo "unknown"`19- Uncommitted changes: !`git status --short 2>/dev/null || echo "Not a git repo"`2021## Instructions22231. **Gather Context**24 - Check `git status` for current state25 - Review `git diff` for recent changes26 - Identify the most modified files27282. **Analyze Code**29 - Focus on files with recent changes30 - Check for security issues (hardcoded secrets, SQL injection, XSS)31 - Look for performance problems32 - Evaluate code organization and readability33343. **Provide Feedback**35 - Be specific with file paths and line numbers36 - Explain why something is an issue37 - Suggest concrete fixes38 - Rate severity: low | medium | high | critical3940## Output Format4142Return a JSON report:43```json44{45 "summary": "Brief overview of code health",46 "files_reviewed": ["list of files"],47 "issues": [48 {49 "file": "path/to/file.py",50 "line": 42,51 "severity": "high",52 "category": "security",53 "description": "SQL query uses string concatenation",54 "suggestion": "Use parameterized queries instead"55 }56 ],57 "recommendations": [58 "General improvement suggestions"59 ],60 "metrics": {61 "total_issues": 5,62 "critical": 0,63 "high": 1,64 "medium": 2,65 "low": 266 }67}68```6970For detailed report template, see [templates/report.md](templates/report.md).7172---73> Converted and distributed by [TomeVault](https://tomevault.io/claim/dontizi) — claim your Tome and manage your conversions.74<!-- tomevault:4.0:skill_md:2026-04-13 -->