From spencergo
Multi-language code review skill with security audit and performance optimization suggestions
How this skill is triggered — by the user, by Claude, or both
Slash command
/spencergo:code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive code review skill that supports:
Comprehensive code review skill that supports:
/spencergo:code-review
Or describe your review needs:
/spencergo:code-review
/path/to/project
Paste code blocks and ask for review:
// Review this code
function getUser(id) {
return db.query(`SELECT * FROM users WHERE id = ${id}`);
}
Provide file path for review:
Review /path/to/src/index.js
Review entire project:
Review my project at ./src
## Code Review Summary
| Category | Issues | Severity |
|----------|--------|----------|
| Security | 3 | HIGH |
| Performance | 2 | MEDIUM |
| Code Quality | 5 | LOW |
| Best Practices | 4 | LOW |
Overall Score: 7/10
For each issue:
## [HIGH] SQL Injection Vulnerability
**File:** src/db.js:15
**Code:**
```javascript
return db.query(`SELECT * FROM users WHERE id = ${id}`);
Problem: User input directly concatenated into SQL query
Suggestion:
return db.query('SELECT * FROM users WHERE id = ?', [id]);
## Supported Languages
| Language | File Extensions |
|----------|-----------------|
| JavaScript | .js, .mjs |
| TypeScript | .ts, .tsx |
| Python | .py |
| Go | .go |
| Java | .java |
| Rust | .rs |
| C++ | .cpp, .cc, .h |
| C# | .cs |
| Ruby | .rb |
| PHP | .php |
## Review Process
1. **Input Recognition** - Determine review type (paste/path/project)
2. **Language Detection** - Auto-detect programming language
3. **Code Parsing** - Understand code structure
4. **Multi-dimensional Review** - Run checks in parallel:
- Security scan
- Performance analysis
- Quality check
- Best practices
5. **Result Aggregation** - Combine all findings
6. **Report Generation** - Format output with severity
## Severity Levels
- **CRITICAL** - Security vulnerabilities, potential data loss
- **HIGH** - Serious bugs, security risks
- **MEDIUM** - Performance issues, maintainability problems
- **LOW** - Style issues, minor improvements
- **INFO** - Suggestions, best practices
## Next Step Guide (MUST FOLLOW)
After code review, you may:
1. **Security issues found** → Recommend `code-review:security` for deeper security analysis
2. **Performance issues found** → Recommend `code-review:performance` for detailed performance analysis
3. **Need fixes applied** → Offer to apply fixes directly
4. **Need explanations** → Provide detailed explanations of any issue
Example transitions:
- "For more detailed security analysis, use /spencergo:code-review:security"
- "I can apply these fixes if you'd like"
- "Would you like me to explain any of these issues in more detail?"
npx claudepluginhub spencerkit/spencergo-marketplace --plugin spencergoPerforms structured code reviews assessing security vulnerabilities, performance issues, maintainability, and best practices with prioritized critical issues and suggestions. For PRs and code feedback.
Conducts thorough code reviews covering security, correctness, performance, maintainability, and testing. Includes automated checks and common vulnerability patterns.
Conducts code reviews assessing quality, best practices, security vulnerabilities, performance, error handling, and test coverage. Outputs categorized issues with recommendations and severity ratings.