lint

Run eslint --fix to auto-fix lint errors in JavaScript and TypeScript projects.

Updated Jun 30, 2026

Search Tags:#automation #TypeScript #eslint #code-quality #JavaScript #static-analysis #lint

Ready to run

npx skills add https://github.com/morgs32/skills --skill lint-morgs32

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/morgs32/skills/tree/main/skills/lint
Command: npx skills add https://github.com/morgs32/skills --skill lint-morgs32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reduce code quality issues by automatically addressing lint errors and applying safe fixes.

Core Features & Use Cases

Auto-fix lint errors with eslint --fix across the project.
Run eslint --fix on the affected file(s) to resolve auto-fixable issues.
If eslint --fix cannot solve a lint error, LEAVE IT TO ME. Do not attempt to manually fix.
NEVER use ESLint disable comments (e.g., eslint-disable-next-line, eslint-disable, etc.). Leave lint errors for the user to fix.

Quick Start

Run eslint --fix on the affected file(s) to resolve auto-fixable lint issues.

Frequently Asked Questions about lint

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

FAQPage Schema

How do I auto-fix lint errors in my JavaScript project?▼

ESLint auto-fix resolves lint errors by running eslint --fix on affected files. This skill safely remediates auto-fixable lint issues in JavaScript and TypeScript codebases without using disable comments.

Can I use this to run ESLint in CI workflows?▼

Yes, this skill supports lint error remediation in development, review, and CI workflows. It automates running eslint --fix to address code quality issues during continuous integration.

What happens to lint errors that eslint --fix cannot solve?▼

When eslint --fix cannot solve a lint error, the skill leaves it for you to fix manually. It strictly avoids using ESLint disable comments like eslint-disable-next-line to hide unresolved issues.

Do I need an existing ESLint configuration to auto-fix TypeScript lint issues?▼

Yes, you need an ESLint configuration in your project and access to the eslint binary. The skill relies on your existing setup to perform static analysis and apply automated fixes.

Why should I avoid using eslint-disable comments for lint errors?▼

Using eslint-disable comments hides code quality issues rather than resolving them. This skill never applies disable comments, leaving unfixable lint errors for you to address properly.