Fix linting and quality issues following root-cause-first philosophy
Fix linting and type issues by addressing root causes first, then safety improvements, and only using documented ignores as a last resort. Use for systematic cleanup of code quality problems.
/plugin marketplace add dhruvbaldawa/ccconfigs/plugin install essentials@ccconfigsFILES OR PATTERNFix quality issues in {{ARGS}} (files, glob pattern, or . for entire project).
1. Fix Root Cause (ALWAYS first)
2. Maintain/Improve Safety & Reliability (if #1 complicates)
3. Local Ignores (ONLY when #1 and #2 both complicate)
1. Gather & Categorize Run linting and type checking tools to collect all issues. Group by: root cause fixable, needs alternative approach, legitimate ignore.
For large codebases (>20 issues): Use TodoWrite to track fixes by category:
☐ Root cause fixes (X issues)
☐ Remove unused imports (N files)
☐ Fix type errors (N issues)
☐ Add missing return types (N functions)
☐ Safety alternatives (Y issues)
☐ Legitimate ignores (Z issues)
☐ Validate all checks pass
☐ Run full test suite
2. Fix in Priority Order
Mark todos completed as you fix each category. This prevents losing track when interrupted.
3. Validate All linting checks + full test suite must pass.
4. Report
✅ Quality Fixed: X root cause, Y alternatives, Z ignores
All checks ✓ | Tests X/X ✓
❌ Blanket disable without justification ❌ Global disable for local issue ❌ Ignoring without understanding why ❌ Fixing symptoms instead of root cause ❌ Making code less safe to silence warnings