fix

# Fix Command $ARGUMENTS Attempts to fix code errors autonomously. ## Usage ```bash /fix <file_or_scope> # Example: /fix src/utils.ts ``` ## Automated Error Classification Before entering the fix loop, classify errors to prioritize auto-fixable ones: ```bash # Pipe lint or test output ruff check . 2>&1 | python3 ${CLAUDE_SKILL_DIR}/scripts/error-classifier.py mypy src/ 2>&1 | python3 ${CLAUDE_SKILL_DIR}/scripts/error-classifier.py npx eslint . 2>&1 | python3 ${CLAUDE_SKILL_DIR}/scripts/error-classifier.py ``` The script outputs JSON with: - **total_errors**: count of all parsed errors - **auto_fixable_count**: errors that tools can fix automatically (e.g., F401 unused imports, formatting) - **manual_count**: errors requiring human/agent intervention - **tools_detected**: which linters produced the output (ruff, mypy, eslint, tsc, phpstan) - **errors[]**: each error with file, line, code, message, and auto_fixable flag - **suggested_order**: files to fix, auto-fixable first - **fix_strategy**: recommended approach (auto-fix first, then manual) Use this to run auto-fixers (e.g., `ruff check --fix .`) before spending time on manual fixes. --- ## Protocol (The "Fix Loop") 1. **Analyze**: Run validation to get the exact error message. ```bash # Get error npm test src/utils.ts 2>&1 | tee error.log ``` 2. **Diagnose**: Analyze `error.log`. - Use `debugging-tactics` skill. - Trace the error to the source line. 3. **Patch**: Apply a fix. - Use `sed` ...