quick-debug

Quick Debug

Usage: /quick-debug or /quick-debug <error-message>

Purpose: Fast debugging workflow for common issues

---

🐛 What This Command Does

Provides AI-assisted debugging workflow to quickly identify and fix common issues:

1. Analyzes error messages and stack traces
2. Suggests likely causes based on patterns
3. Recommends debugging steps
4. Provides quick fixes for common problems
5. Links to relevant code locations

---

🔍 Debugging Workflow

Step 1: Capture Error Information

If error message provided as argument:

# Use provided error
ERROR_MSG="$ARGUMENTS"
```bash
If no argument, look for recent errors:
```bash
# Check recent test failures
uv run --frozen pytest --lf -v 2>&1 | tee /tmp/test_errors.txt

# Check recent git commits for fix mentions
git log -10 --oneline | grep -i "fix"

# Check application logs (if running)
tail -50 logs/app.log 2>/dev/null || echo "No app logs found"

Step 2: Categorize Error Type

Analyze error message to determine category:

Import Errors:

ImportError: cannot import name 'X'
ModuleNotFoundError: No module named 'X'

→ Missing dependency, uncommitted code, wrong Python env

Test Failures:

AssertionError: X != Y
AttributeError: 'NoneType' object has no attribute 'X'

→ Logic error, missing mock, incorrect test setup

Runtime Errors:

RuntimeError: Event loop is closed
asyncio.TimeoutError: timeout exceeded

→ Async issues, resource management, timeouts

Type Errors:

TypeError: X() takes 2 positional arguments but 3 were given
mypy error: Argument has incompatible type

→ Function signature mismatch, type annotation issues

Database/Connection Errors:

ConnectionError: Failed to connect to Redis
sqlalchemy.exc.OperationalError

→ Service not running, configuration issue, network problem

Step 3: AI-Assisted Analysis

Provide context to Claude for analysis:

Analyzing error: {error_message}

Error Category: {category}
Recent Changes: {git log -5}
Modified Files: {git diff --name-only}
Test Status: {pytest status}

Please analyze this error and suggest:
1. Most likely root cause
2. Quick diagnostic steps
3. Potential fixes
4. Similar issues in codebase