Fix Errors

Workflow

1. DISCOVER COMMANDS: Check

   package.json

   for exact script names
   • Look for:

     lint

     ,

     typecheck

     ,

     type-check

     ,

     tsc

     ,

     eslint

     ,

     prettier

     ,

     format

2. RUN DIAGNOSTICS:
   • Run

     pnpm run lint

     (or equivalent)
   • Run

     pnpm run typecheck

     or

     tsc --noEmit

   • Capture all error output
3. ANALYZE ERRORS:
   • Extract file paths from error messages
   • Group errors by file location
   • Count total errors and affected files
4. CREATE ERROR AREAS:
   • MAX 5 FILES PER AREA
   • Group related files together (same directory/feature)
   • Example:

     Area 1: [file1, file2, file3, file4, file5]

5. PARALLEL PROCESSING: Launch snipper agents for each area
   • Use Task tool with multiple agents simultaneously
   • Each agent processes one area (max 5 files)
   • Provide specific error details for each file
6. VERIFICATION: Re-run diagnostics after fixes
   • Wait for all agents to complete
   • Re-run lint and typecheck
   • Report remaining errors
7. FORMAT CODE: Apply Prettier (if available)
   • Run

     pnpm run format

     or equivalent

Snipper Agent Instructions

Fix all ESLint and TypeScript errors in these files:
[list of files with their specific errors]

Focus only on these files. Make minimal changes to fix errors while preserving functionality.

Rules

• ALWAYS check package.json first for correct commands
• ONLY fix linting and TypeScript errors
• NO feature additions - minimal fixes only
• PARALLEL ONLY - use Task tool for concurrent processing
• Every error must be assigned to an area