/fix-errors

Overview

Automatically identifies and fixes all ESLint and TypeScript errors by breaking them into manageable areas and processing them in parallel using snipper agents.

Usage

/fix-errors

How It Works

1. Discovers Commands - Checks package.json for lint, typecheck, and format scripts
2. Runs Diagnostics - Executes linting and type-checking to capture all errors
3. Analyzes Errors - Parses and categorizes errors by file location
4. Creates Areas - Organizes files into groups (max 5 files per area)
5. Parallel Processing - Launches snipper agents for each area concurrently
6. Verification - Re-runs diagnostics after all fixes complete
7. Formats Code - Applies Prettier formatting as final step

Key Features

• Parallel Processing - Multiple areas fixed simultaneously for speed
• Smart Grouping - Related files grouped together (max 5 per area)
• Minimal Changes - Only fixes errors, preserves functionality
• Complete Coverage - Every error-containing file gets fixed

Execution Rules

• Always checks package.json for correct command names
• Focuses only on linting and TypeScript errors
• No feature additions, minimal fixes only
• Uses Task tool for concurrent processing
• All errors assigned to areas for systematic fixing

When to Use

• Codebase has multiple ESLint or TypeScript errors
• Need to fix all errors quickly and systematically
• Want parallel processing for faster fixes
• After major refactoring that introduced many errors