debug-systematic
Systematic Debugging Workflow
I'll help you debug issues systematically using the scientific method - hypothesis formation, testing, and iterative refinement.
Arguments: $ARGUMENTS - error description, reproduction steps, or context
Token Optimization
Target: 50% reduction (4,000-6,000 → 1,500-3,000 tokens)
Core Optimization Strategies
1. Hypothesis-Driven Debugging (Not Exhaustive Analysis)
- ❌ AVOID: Reading entire codebase to find bugs
- ✅ DO: Form hypotheses about likely causes, test top 2-3 first
- Token savings: 90% (200 tokens vs 2,000+ tokens)
- Pattern: Prioritize recently changed files, common failure patterns
2. Git Diff for Recently Changed Files (Likely Bug Source)
More from manastalukdar/claude-devstudio
duplication-detect
Find and eliminate code duplication with DRY refactoring strategies
20db-diagram
Generate database ER diagrams from schema for documentation
17lighthouse
Run Lighthouse audits and implement performance, accessibility, and SEO fixes
13session-resume
Resume previous work from archived session with full context restoration
12owasp-check
OWASP Top 10 vulnerability scanning and remediation
12database-connect
Database MCP server integration for PostgreSQL, MySQL, MongoDB
11