Fix Linter Errors

Target rules: $ARGUMENTS

If no arguments provided, prompt the user for at least one lint rule name.

Step 1: Gather Requirements

• Parse rules from $ARGUMENTS (space-separated)

• Run linter to collect all violations: bun run lint 2>&1

• Group violations by rule, then by file, noting:

• File path and line numbers

• Violation count per file

• Sample error messages

Step 2: Compile Brief and Delegate

Compile the gathered information into a structured brief:

Fix ESLint violations for rules: $ARGUMENTS

Violations by rule:

• [rule-name-1]: X total violations across Y files
  • [file]: N violations (lines: ...)
  • ...
• [rule-name-2]: X total violations across Y files
  • ...

Fix strategies: extract functions, early returns, apply formatting, add types

Verification: bun run lint 2>&1 | grep -E "($ARGUMENTS)" | wc -l → Expected: 0

Invoke /plan-execute with this brief to create the implementation plan.