dobroslavradosavljevic Review Code Skill
Trigger Phrases
This skill is automatically triggered when the user:
- Asks to "review", "check", "audit", or "analyze" code
- Requests code quality assessment
- Wants feedback on implementation
- Says things like "look at", "evaluate", or "inspect" code
- Asks for suggestions or improvements on existing code
- Mentions "code review" or "quality check"
Delegation Instructions
When this skill is triggered:
- Delegate immediately to the
code-revieweragent - Pass the file paths or code to be reviewed
- Include any specific concerns or focus areas
- Specify the type of review requested (security, performance, style, etc.)
- Include project standards context
Context to Pass
- Files to Review: Specific file paths or directories
- Review Focus: Areas of concern (security, performance, readability)
- Project Standards: Coding conventions from CLAUDE.md
- Scope: Full review vs. specific aspects
- Comparison: Any reference implementations to compare against
- Priority: Critical issues vs. general review
Agent Responsibilities
The code-reviewer agent will:
- Read and analyze the specified code
- Check for adherence to project coding standards
- Identify potential bugs, security issues, or performance problems
- Evaluate code structure and maintainability
- Provide actionable feedback and suggestions
- Report findings in a structured format with severity levels
Usage Examples
Example 1: General Review
User: "Review the authentication code"
Delegation: Delegate to code-reviewer with:
- Files: Authentication-related files
- Focus: General code quality
- Standards: Project coding standards
Example 2: Security Review
User: "Check the API endpoints for security issues"
Delegation: Delegate to code-reviewer with:
- Files: API endpoint files
- Focus: Security vulnerabilities
- Standards: Security best practices
Example 3: Performance Review
User: "Review this code for performance issues"
Delegation: Delegate to code-reviewer with:
- Files: Specific code files
- Focus: Performance optimization
- Context: Performance requirements
Best Practices
- Always delegate code reviews to code-reviewer
- Specify review focus clearly
- Include project standards
- Provide file paths or code
- Request prioritized findings