Perform thorough code review analyzing quality, potential bugs, security issues, and suggesting improvements.
Parameters
{
"type": "object",
"properties": {
"target": {
"type": "string",
"description": "File path, directory, or glob pattern to review"
},
"focus": {
"type": "string",
"enum": ["general", "security", "performance", "maintainability"],
"description": "Primary focus area",
"default": "general"
}
},
"required": ["target"]
}
When to Use
- User asks to "review" or "check" code
- User wants to find bugs or issues
- User asks about code quality
- User wants security analysis
- User asks for improvement suggestions
Methodology
Phase 1: Context Gathering
- Read the target files
- Understand the codebase structure
- Identify the programming language and framework
- Check for related tests and documentation
Phase 2: Analysis
- Logic Review: Check for bugs and edge cases
- Security Scan: Look for vulnerabilities (injection, auth issues, etc.)
- Performance Check: Identify bottlenecks and inefficiencies
- Style Review: Check consistency and best practices
Phase 3: Prioritization
- Categorize issues by severity (Critical, High, Medium, Low)
- Focus on actionable feedback
- Provide concrete examples
Phase 4: Output
Provide structured review with:
- Summary of findings
- Issues list with severity and line numbers
- Specific improvement suggestions
- Code examples where helpful
Guidelines
- Be constructive, not just critical
- Provide specific line references
- Explain WHY something is an issue
- Suggest concrete fixes, not just problems
- Acknowledge good patterns when found
- Consider the project's existing style
Examples
Example 1: File Review
User Input: "Review src/auth.ts for security issues"
Expected Behavior:
- Read the file and understand authentication flow
- Check for common security issues (SQL injection, XSS, weak crypto)
- Verify input validation and sanitization
- Check for proper error handling
- Provide prioritized list of findings with fixes
Example 2: Directory Review
User Input: "Help me review the code quality of the src/utils/ directory"
Expected Behavior:
- List and read all files in the directory
- Analyze code structure, naming, and error handling
- Check for duplicate code or patterns that can be abstracted
- Output a detailed review report in Chinese
- List issues sorted by severity