fix-eslint

Fix ESLint errors in JavaScript and TypeScript projects without disabling rules.

4|Updated Oct 6, 2025
One-click install
npx skills add https://github.com/otrebu/agents --skill fix-eslint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-eslint
Source: https://github.com/otrebu/agents/tree/main/skills/fix-eslint
Command: npx skills add https://github.com/otrebu/agents --skill fix-eslint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm, eslint, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually fixing ESLint errors is a repetitive, time-consuming, and often inconsistent task, especially in large codebases. This leads to developer fatigue and compromises code quality. This Skill automates the entire ESLint fixing process.

Core Features & Use Cases

  • Smart Fixing Strategy: Directly fixes small error counts (≤20) and intelligently orchestrates parallel sub-agents for larger codebases (>20 errors) by directory for efficient processing.
  • Compliance-Focused: Modifies code to comply with linting rules; it never disables rules, adds ignore comments, or alters ESLint configurations.
  • Functionality Preservation: Ensures that all fixes maintain existing code behavior and strictly adhere to project coding standards (e.g., FP-first style, explicit naming).
  • Use Case: When your project has accumulated numerous ESLint errors, simply ask Claude to "fix ESLint errors in src/." It will intelligently analyze and apply fixes, either directly or by spawning parallel agents, saving you hours of manual correction and ensuring consistent code quality.

Quick Start

Fix all ESLint errors in the current project, ensuring no rules are disabled.

Frequently Asked Questions about fix-eslint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix ESLint errors in my JavaScript or TypeScript project?

ESLint errors can be fixed automatically by analyzing your codebase and modifying source code to satisfy linting rules. This Skill scans for ESLint violations, applies direct fixes for small error counts (≤20 errors) and spawns parallel agents by directory for larger codebases (>20 errors), then validates fixes by re-running lint to ensure compliance.

Does this approach work for both small and large codebases?

Yes. For projects with 20 or fewer ESLint errors, fixes are applied directly. For larger error volumes, the Skill intelligently orchestrates parallel sub-agents per directory to process fixes efficiently while maintaining code consistency and preserving existing functionality.

Can I fix ESLint errors without disabling rules or adding ignore comments?

Yes. This Skill modifies code to comply with linting rules rather than bypassing them. It never disables rules, adds eslint-disable comments, or alters ESLint configurations—it fixes the actual implementation to satisfy lint rules while adhering to your project's coding standards.

What happens to my code's functionality when ESLint errors are fixed?

All fixes maintain existing code behavior and functionality. The Skill strictly adheres to your project's coding standards (such as functional programming or explicit naming conventions) while resolving lint violations, ensuring the fixed code remains correct and consistent.

What tools and setup do I need to fix ESLint errors?

You need pnpm as your package manager and ESLint installed in your project. The Skill works with JavaScript and TypeScript projects that already have ESLint configured; it requires no additional configuration or setup beyond these dependencies.