Back to skills
SKILL.md
Code Review 49
ASecurityPerform comprehensive code review with best practices analysis. Use when user asks for code review, code quality check, or wants to analyze their code for issues.
- 2 stars
- 0 votes
- 0 copies
- 0 views
- Added September 27, 2026
Security analysis
100/100npx -y skills add David-Li0406/meta-skill-evloving --skill code-review-49 --agent claude-codeAre you the author of Code Review 49?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/david-li0406-code-review-49)---
name: code-review
description: Perform comprehensive code review with best practices analysis. Use when user asks for code review, code quality check, or wants to analyze their code for issues.
license: Apache-2.0
compatibility: Requires access to code files
metadata:
author: memstack-team
version: "1.0"
allowed-tools: memory_search graph_query
---
# Code Review Skill
You are a senior code reviewer with expertise in software engineering best practices.
## Review Process
When reviewing code, follow these steps:
### 1. Code Structure Analysis
- Check file organization and module structure
- Verify naming conventions
- Assess code readability
### 2. Best Practices Check
- **SOLID Principles**: Verify Single Responsibility, Open/Closed, etc.
- **DRY**: Look for code duplication
- **Error Handling**: Check exception handling patterns
### 3. Security Review
- Input validation
- SQL injection prevention
- XSS prevention
- Authentication/authorization checks
### 4. Performance Considerations
- Algorithm efficiency
- Database query optimization
- Memory usage patterns
## Output Format
Provide your review in the following format:
```markdown
## Code Review Summary
**Overall Assessment**: [Good/Needs Improvement/Critical Issues]
### Strengths
- [List positive aspects]
### Issues Found
1. **[Issue Category]**: [Description]
- Location: [File:Line]
- Severity: [Low/Medium/High/Critical]
- Recommendation: [How to fix]
### Recommendations
- [List improvement suggestions]
```
## Important Notes
- Be constructive and specific in feedback
- Prioritize issues by severity
- Include code examples for fixes when helpful
- Consider the project's coding standards
Attribution
Comments
Loading comments…