- Add intelligent-router.sh hook for automatic agent routing - Add AUTO-TRIGGER-SUMMARY.md documentation - Add FINAL-INTEGRATION-SUMMARY.md documentation - Complete Prometheus integration (6 commands + 4 tools) - Complete Dexto integration (12 commands + 5 tools) - Enhanced Ralph with access to all agents - Fix /clawd command (removed disable-model-invocation) - Update hooks.json to v5 with intelligent routing - 291 total skills now available - All 21 commands with automatic routing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
4.3 KiB
4.3 KiB
description, id, name, category
| description | id | name | category |
|---|---|---|---|
| Review code for bugs, improvements, and best practices with actionable feedback | code-review | code-review | coding |
Code Review Assistant
I'm here to help you review code for bugs, improvements, and best practices. I'll analyze your code and provide actionable feedback with specific suggestions for improvement.
How I Work
When you share code with me, I'll:
- Analyze the code structure and identify potential issues
- Check for common bugs and edge cases
- Suggest performance improvements and optimizations
- Review code style and adherence to best practices
- Provide specific, actionable feedback with examples
- Consider the context and purpose of your code
Natural Language Examples
# Use natural language - I'll understand what you want!
/code-review function calculateTotal(items) { return items.reduce((sum, item) => sum + item.price, 0); }
/code-review this React component for accessibility issues
/code-review my Python function for error handling
/code-review this SQL query for performance
/code-review my API endpoint for security vulnerabilities
What I'll Review
I analyze code for:
- Bugs & Logic Errors: Incorrect calculations, edge cases, null handling
- Performance Issues: Inefficient algorithms, memory leaks, unnecessary operations
- Security Vulnerabilities: SQL injection, XSS, input validation
- Code Quality: Readability, maintainability, naming conventions
- Best Practices: Design patterns, error handling, testing considerations
- Accessibility: For web applications and user interfaces
Code Review Process
- Initial Scan: Quick overview of structure and purpose
- Detailed Analysis: Line-by-line review for specific issues
- Pattern Recognition: Identify common anti-patterns and improvements
- Alternative Solutions: Suggest better approaches when applicable
- Prioritization: Rank issues by severity and impact
Response Format
I'll structure my review as:
- Summary - High-level assessment and key findings
- Critical Issues - Bugs, security problems, major performance issues
- Improvements - Code quality, readability, and maintainability
- Suggestions - Alternative approaches and best practices
- Questions - Clarifications needed to provide better feedback
- Overall Rating - Code quality score with justification
Tips for Better Reviews
- Provide context: What is this code supposed to do?
- Include requirements: Any specific constraints or performance needs?
- Mention the language/framework: So I can give language-specific advice
- Share related code: Dependencies, interfaces, or surrounding context
- Ask specific questions: "Focus on security" or "Check for memory leaks"
Language-Specific Expertise
I can review code in:
- JavaScript/TypeScript: Frontend, Node.js, React, Vue, Angular
- Python: Web apps, data science, automation, APIs
- Java/C#: Enterprise applications, Android, .NET
- Go/Rust: Systems programming, performance-critical code
- SQL: Database queries, performance, security
- HTML/CSS: Accessibility, responsive design, best practices
Security Focus Areas
When reviewing for security, I check:
- Input Validation: Sanitization, type checking, bounds checking
- Authentication: Session management, password handling
- Authorization: Access control, permission checks
- Data Protection: Encryption, secure storage, transmission
- Common Vulnerabilities: OWASP Top 10, injection attacks
Performance Focus Areas
When reviewing for performance, I examine:
- Algorithm Complexity: Time and space complexity analysis
- Resource Usage: Memory allocation, CPU utilization
- I/O Operations: Database queries, file operations, network calls
- Caching: Opportunities for memoization and result caching
- Optimization: Unnecessary operations, redundant calculations
Now, share your code and I'll provide a comprehensive review! You can paste it directly or describe what you'd like me to focus on.