feat: Add intelligent auto-router and enhanced integrations
- 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>
This commit is contained in:
admin
103
dexto/commands/code-review.md
Normal file
103
dexto/commands/code-review.md
Normal file
@@ -0,0 +1,103 @@
|
||||
---
|
||||
description: "Review code for bugs, improvements, and best practices with actionable feedback"
|
||||
id: code-review
|
||||
name: code-review
|
||||
category: coding
|
||||
---
|
||||
|
||||
<!-- TODO: (355) Move all prompts off absolute path and into relative agent specific paths, referenced using @dexto.agent_dir colocated near their folders. This allows us to keep agent specific prompts -->
|
||||
<!-- https://github.com/truffle-ai/dexto/pull/355#discussion_r2413003414 -->
|
||||
# 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:
|
||||
|
||||
1. **Analyze the code structure** and identify potential issues
|
||||
2. **Check for common bugs** and edge cases
|
||||
3. **Suggest performance improvements** and optimizations
|
||||
4. **Review code style** and adherence to best practices
|
||||
5. **Provide specific, actionable feedback** with examples
|
||||
6. **Consider the context** and purpose of your code
|
||||
|
||||
## Natural Language Examples
|
||||
|
||||
```bash
|
||||
# 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
|
||||
|
||||
1. **Initial Scan**: Quick overview of structure and purpose
|
||||
2. **Detailed Analysis**: Line-by-line review for specific issues
|
||||
3. **Pattern Recognition**: Identify common anti-patterns and improvements
|
||||
4. **Alternative Solutions**: Suggest better approaches when applicable
|
||||
5. **Prioritization**: Rank issues by severity and impact
|
||||
|
||||
## Response Format
|
||||
|
||||
I'll structure my review as:
|
||||
|
||||
1. **Summary** - High-level assessment and key findings
|
||||
2. **Critical Issues** - Bugs, security problems, major performance issues
|
||||
3. **Improvements** - Code quality, readability, and maintainability
|
||||
4. **Suggestions** - Alternative approaches and best practices
|
||||
5. **Questions** - Clarifications needed to provide better feedback
|
||||
6. **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.
|
||||
|
||||
Reference in New Issue
Block a user