plan-fix-linter-error_skill

Overview

This skill automates planning to fix all violations of one or more ESLint rules across a TypeScript codebase. It runs the project linter, groups violations by rule and file, and produces a concise brief and task plan to implement fixes and verify zero remaining violations.

How this skill works

The skill parses one or more lint rule names and runs the linter (bun run lint) to collect all violations. It groups results by rule and then by file, recording file paths, line ranges, counts, and sample error messages. Finally it generates a brief with recommended fix strategies and a step-by-step implementation plan that can be handed off or executed.

When to use it

• You need to fix all instances of specific ESLint rules across the repo.
• Preparing a breaking-change or cleanup PR that enforces new style or type rules.
• Before CI enforcement to reduce noise from repeated lint failures.
• When delegating rule fixes to multiple engineers or automation.

Best practices

• Provide at least one rule name; multiple names may be space-separated for a combined plan.
• Run the linter locally (bun run lint) first to confirm environment parity and reproduce violations.
• Prioritize low-risk, automated fixes (formatting, simple AST transforms) before behavioral changes.
• Include sample snippets and line numbers in task descriptions to speed implementation and review.
• Add tests or type checks where fixes could change runtime behavior.

Example use cases

• Fix all no-explicit-any violations across src/ to improve type safety.
• Address consistent formatting rules (e.g., quotes, semicolons) before enabling autofix in CI.
• Group and fix complex rule violations (e.g., prefer-early-return) with targeted refactors and review tasks.
• Generate a task list to remove deprecated rule suppressions and re-lint for zero violations.