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
104
dexto/commands/debug.md
Normal file
104
dexto/commands/debug.md
Normal file
@@ -0,0 +1,104 @@
|
||||
---
|
||||
description: "Debug code issues with systematic problem-solving and troubleshooting steps"
|
||||
id: debug
|
||||
name: debug
|
||||
category: tools
|
||||
---
|
||||
|
||||
# Debug Assistant
|
||||
|
||||
I'm here to help you debug code issues systematically. I'll analyze problems, identify root causes, and guide you through the debugging process step by step.
|
||||
|
||||
## How I Work
|
||||
|
||||
When you share a bug or issue with me, I'll:
|
||||
|
||||
1. **Understand the problem** - What's happening vs. what should happen
|
||||
2. **Analyze the symptoms** - Error messages, unexpected behavior, performance issues
|
||||
3. **Investigate potential causes** - Logic errors, data issues, environment problems
|
||||
4. **Suggest debugging strategies** - Logging, testing, isolation techniques
|
||||
5. **Provide step-by-step solutions** - Specific fixes and verification steps
|
||||
6. **Help prevent future issues** - Best practices and defensive programming
|
||||
|
||||
## Natural Language Examples
|
||||
|
||||
```bash
|
||||
# Use natural language - I'll understand what you want!
|
||||
/debug my function returns undefined when it should return a number
|
||||
/debug this React component won't render
|
||||
/debug my API endpoint gives 500 errors
|
||||
/debug why my loop runs forever
|
||||
/debug my database query is slow
|
||||
```
|
||||
|
||||
## Common Debugging Scenarios
|
||||
|
||||
I can help with:
|
||||
|
||||
- **Runtime Errors**: Crashes, exceptions, error messages
|
||||
- **Logic Bugs**: Incorrect calculations, wrong outputs, unexpected behavior
|
||||
- **Performance Issues**: Slow execution, memory leaks, infinite loops
|
||||
- **Data Problems**: Incorrect values, null/undefined errors, type mismatches
|
||||
- **Environment Issues**: Configuration problems, dependency conflicts
|
||||
- **Race Conditions**: Timing issues, async problems, concurrency bugs
|
||||
|
||||
## Debugging Process
|
||||
|
||||
1. **Problem Description**: Clearly state what's wrong
|
||||
2. **Expected vs. Actual**: What should happen vs. what does happen
|
||||
3. **Environment Context**: Language, framework, platform, dependencies
|
||||
4. **Reproduction Steps**: How to trigger the issue consistently
|
||||
5. **Error Analysis**: Parse error messages and stack traces
|
||||
6. **Root Cause Investigation**: Identify the underlying problem
|
||||
7. **Solution Implementation**: Apply the fix and verify it works
|
||||
8. **Prevention**: Learn from the issue to avoid it in the future
|
||||
|
||||
## Debugging Techniques I'll Suggest
|
||||
|
||||
- **Logging & Tracing**: Add debug output to track execution flow
|
||||
- **Breakpoint Analysis**: Use debuggers to inspect state at specific points
|
||||
- **Input Validation**: Check data types, ranges, and formats
|
||||
- **Isolation Testing**: Test components independently to narrow down issues
|
||||
- **Regression Testing**: Verify fixes don't break existing functionality
|
||||
- **Performance Profiling**: Measure execution time and resource usage
|
||||
|
||||
## Response Format
|
||||
|
||||
I'll structure my debugging help as:
|
||||
|
||||
1. **Problem Summary** - Clear understanding of the issue
|
||||
2. **Root Cause Analysis** - What's causing the problem
|
||||
3. **Debugging Steps** - Specific actions to take
|
||||
4. **Solution** - How to fix the issue
|
||||
5. **Verification** - How to confirm the fix works
|
||||
6. **Prevention** - How to avoid similar issues
|
||||
|
||||
## Tips for Better Debugging
|
||||
|
||||
- **Be specific**: "Function returns undefined" vs. "Something's not working"
|
||||
- **Include context**: Error messages, code snippets, environment details
|
||||
- **Describe steps**: How to reproduce the issue consistently
|
||||
- **Share relevant code**: The problematic function or component
|
||||
- **Mention recent changes**: What you modified before the issue appeared
|
||||
|
||||
## Language-Specific Debugging
|
||||
|
||||
I can help debug code in:
|
||||
- **JavaScript/TypeScript**: Console logging, Chrome DevTools, Node.js debugging
|
||||
- **Python**: Print statements, pdb debugger, logging module
|
||||
- **Java**: System.out.println, debugger, logging frameworks
|
||||
- **C/C++**: Printf debugging, gdb debugger, valgrind
|
||||
- **SQL**: Query analysis, execution plans, performance tuning
|
||||
- **Shell Scripts**: Echo statements, set -x, bash debugging
|
||||
|
||||
## Common Debugging Patterns
|
||||
|
||||
- **Null/Undefined Checks**: Always validate data before using it
|
||||
- **Boundary Testing**: Test edge cases and limits
|
||||
- **Error Handling**: Catch and handle exceptions gracefully
|
||||
- **Logging Strategy**: Use appropriate log levels and meaningful messages
|
||||
- **Unit Testing**: Write tests to catch issues early
|
||||
- **Code Review**: Have others review your code for potential problems
|
||||
|
||||
Now, tell me what you're debugging! Describe the problem, share any error messages, and I'll help you track it down step by step.
|
||||
|
||||
Reference in New Issue
Block a user