← Back to list

debugger
by VenTheZone
The AI coding self evolving agent built for the terminal - Built on top of opencode
⭐ 4🍴 0📅 Jan 21, 2026
SKILL.md
name: debugger description: Systematic debugging and troubleshooting for code and infrastructure issues license: MIT compatibility: opencode metadata: audience: developers workflow: troubleshooting
Debugger
What I do
- Analyze error messages and stack traces
- Systematic troubleshooting of code issues
- Debug build and deployment failures
- Performance analysis and optimization
- Log analysis and monitoring setup
- Network and API debugging
- Database query optimization
- Memory leak detection
When to use me
Use this when you encounter:
- Runtime errors and exceptions
- Build failures and compilation errors
- Performance bottlenecks
- Memory leaks or resource issues
- Network connectivity problems
- Database performance issues
- Test failures and flaky tests
- Deployment and infrastructure problems
Debugging methodology I follow
- Reproduce the issue: Understand the exact conditions
- Gather information: Collect logs, error messages, context
- Formulate hypotheses: Identify potential root causes
- Test hypotheses: Verify each potential cause systematically
- Implement fixes: Apply targeted solutions
- Verify resolution: Ensure the issue is fully resolved
- Prevent recurrence: Add safeguards and monitoring
Areas I can debug
- Application code: Logic errors, bugs, exceptions
- Build systems: Compilation, dependency issues
- Infrastructure: Docker, Kubernetes, cloud services
- Databases: Queries, connections, performance
- Networks: APIs, services, connectivity
- Performance: CPU, memory, I/O bottlenecks
- Security: Authentication, authorization, vulnerabilities
Tools I can use
- Debuggers: gdb, pdb, Chrome DevTools
- Profilers: perf, flame graphs, memory profilers
- Log analysis: grep, awk, log aggregation tools
- Network tools: curl, wget, tcpdump, Wireshark
- Monitoring: Prometheus, Grafana, custom metrics
- Static analysis: Linters, security scanners
- Testing frameworks: Unit tests, integration tests
Common patterns I recognize
- Null pointer exceptions and undefined behavior
- Race conditions and concurrency issues
- Memory leaks and resource management
- Timeout and connection issues
- Configuration and environment problems
- Version compatibility issues
- Security misconfigurations
Prevention strategies I recommend
- Comprehensive testing strategies
- Proper error handling and logging
- Code reviews and static analysis
- Monitoring and alerting setup
- Documentation and knowledge sharing
- Regular security audits
- Performance testing and optimization
Ask me to debug any issue, and I'll systematically identify and resolve the root cause.
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon