eslint

Configure and run ESLint to enforce JavaScript/TypeScript coding standards.

7|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill eslint-joabgonzalez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eslint
Source: https://github.com/joabgonzalez/ai-agents-skills/tree/main/skills/eslint
Command: npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill eslint-joabgonzalez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ESLint enforces consistent code quality and style across JavaScript and TypeScript projects, catching errors early and enabling maintainable codebases.

Core Features & Use Cases

  • TypeScript-aware linting with @typescript-eslint/parser and recommended rules for strong type safety.
  • Configurable rules & plugins to tailor coding standards, enforce no-explicit-any, and ensure import organization.
  • CI and editor integration to run lint checks on commit, pull requests, and in development environments across monorepos.

Quick Start

Install ESLint in your project, configure a rule set, and run lint locally or in CI.

Frequently Asked Questions about eslint

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

FAQPage Schema
How do I configure ESLint for a TypeScript project to enforce no-explicit-any?

Yes, ESLint can be integrated into CI pipelines and editor environments to run lint checks on commits and pull requests. This integration catches issues early during development and continuous integration across monorepos.

What is the best way to manage import organization and code quality in a JavaScript monorepo?

The best way to manage code quality in a JavaScript monorepo is by configuring ESLint with tailored rules and plugins. This enforces coding standards, ensures import organization, and maintains consistency across diverse project setups.

Does ESLint work with continuous integration pipelines to catch code quality issues?

Yes, ESLint integrates with CI pipelines to run automated lint checks during continuous integration. This enforces high-quality JavaScript and TypeScript code standards by catching errors before deployment across monorepos and single-repo apps.

Can I enforce consistent coding standards across different JavaScript and TypeScript project setups?

Yes, you can enforce consistent coding standards across different setups by configuring ESLint with customizable rules and plugins. This catches errors early and enables maintainable codebases in single-repo apps, monorepos, and CI pipelines.

Why should I use the TypeScript parser for ESLint instead of default JavaScript linting?

You should use the TypeScript parser for ESLint to enable TypeScript-aware linting with recommended rules for strong type safety. This ensures the linter understands TypeScript syntax and enforces type-level constraints like no-explicit-any.