eslint-checker

ESLint executes static analysis on your JavaScript and TypeScript files using your project's eslint.config.js or .eslintrc.* configuration file. Point it at your source directories, and it reports style violations, potential bugs, and code-quality issues against your configured rules.

ESLint can auto-fix many violations—formatting inconsistencies, unused variables, and rule-compliant replacements—when you enable the fix option. The Skill prompts for confirmation on multiple configs or unclear scopes before applying fixes, then outputs a diff of changes made.

You need Node.js and npm installed, a valid eslint.config.js or .eslintrc configuration file in your project, and target files or directories to lint. The Skill runs ESLint commands against your specified paths and outputs diagnostics if config issues are detected.

Yes, ESLint performs static analysis and style enforcement on both JavaScript and TypeScript source files. Your eslint configuration determines which rules apply, and the Skill applies fixes across both file types in your specified directories.

The Skill generates a readable lint summary or HTML report that can be shared. ESLint produces detailed output showing violations by file, rule, severity, and line number, making it easy to communicate issues and fixes to collaborators.

ESLint reports all violations—both auto-fixable and manual—in its output. Non-fixable violations require manual code edits to resolve. The Skill distinguishes fixable from manual issues so you know which require developer attention.