mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
3802bca865
Plugin Scope Improvements: - Remove language-specialists plugin (not task-focused) - Split specialized-domains into 5 focused plugins: * blockchain-web3 - Smart contract development only * quantitative-trading - Financial modeling and trading only * payment-processing - Payment gateway integration only * game-development - Unity and Minecraft only * accessibility-compliance - WCAG auditing only - Split business-operations into 3 focused plugins: * business-analytics - Metrics and reporting only * hr-legal-compliance - HR and legal docs only * customer-sales-automation - Support and sales workflows only - Fix infrastructure-devops scope: * Remove database concerns (db-migrate, database-admin) * Remove observability concerns (observability-engineer) * Move slo-implement to incident-response * Focus purely on container orchestration (K8s, Docker, Terraform) - Fix customer-sales-automation scope: * Remove content-marketer (unrelated to customer/sales workflows) Marketplace Statistics: - Total plugins: 27 (was 22) - Tool coverage: 100% (42/42 tools referenced) - Fat plugins removed: 3 (language-specialists, specialized-domains, business-operations) - All plugins now have clear, focused tasks Model Migration: - Migrate all 42 tools from claude-sonnet-4-0/opus-4-1 to model: sonnet - Migrate all 15 workflows from claude-opus-4-1 to model: sonnet - Use short model syntax consistent with agent files Documentation Updates: - Update README.md with refined plugin structure - Update plugin descriptions to be task-focused - Remove anthropomorphic and marketing language - Improve category organization (now 16 distinct categories) Ready for October 9, 2025 @ 9am PST launch
2.1 KiB
2.1 KiB
model
| model |
|---|
| sonnet |
Debug complex issues using specialized debugging agents:
[Extended thinking: This tool command leverages the debugger agent with additional support from performance-engineer when performance issues are involved. It provides deep debugging capabilities with root cause analysis.]
Debugging Approach
1. Primary Debug Analysis
Use Task tool with subagent_type="debugger" to:
- Analyze error messages and stack traces
- Identify code paths leading to the issue
- Reproduce the problem systematically
- Isolate the root cause
- Suggest multiple fix approaches
Prompt: "Debug issue: $ARGUMENTS. Provide detailed analysis including:
- Error reproduction steps
- Root cause identification
- Code flow analysis leading to the error
- Multiple solution approaches with trade-offs
- Recommended fix with implementation details"
2. Performance Debugging (if performance-related)
If the issue involves performance problems, also use Task tool with subagent_type="performance-engineer" to:
- Profile code execution
- Identify bottlenecks
- Analyze resource usage
- Suggest optimization strategies
Prompt: "Profile and debug performance issue: $ARGUMENTS. Include:
- Performance metrics and profiling data
- Bottleneck identification
- Resource usage analysis
- Optimization recommendations
- Before/after performance projections"
Debug Output Structure
Root Cause Analysis
- Precise identification of the bug source
- Explanation of why the issue occurs
- Impact analysis on other components
Reproduction Guide
- Step-by-step reproduction instructions
- Required environment setup
- Test data or conditions needed
Solution Options
-
Quick Fix - Minimal change to resolve issue
- Implementation details
- Risk assessment
-
Proper Fix - Best long-term solution
- Refactoring requirements
- Testing needs
-
Preventive Measures - Avoid similar issues
- Code patterns to adopt
- Tests to add
Implementation Guide
- Specific code changes needed
- Order of operations for the fix
- Validation steps
Issue to debug: $ARGUMENTS