ESLint MCP Integration

Run ESLint code linting and analysis through the Model Context Protocol (MCP) server to check code quality, enforce style guidelines, and detect errors in JavaScript and TypeScript projects.

What This Skill Does

This skill enables AI assistants to:

Instructions

When the user requests code linting, ESLint analysis, or mentions code quality checks:

1. **Verify ESLint availability**: Check if ESLint is available in the project by looking for:

- `eslint` in `package.json` dependencies

- `.eslintrc.*` or `eslint.config.js` configuration files

- If not present, inform the user ESLint needs to be installed first

2. **Run ESLint via MCP**: Use one of these commands:

```bash

npx @eslint/mcp

```

Or if ESLint CLI is available:

```bash

npx eslint --mcp

```

3. **Analyze results**: Review the linting output for:

- Errors (must be fixed)

- Warnings (should be addressed)

- File locations and line numbers

- Rule violations with rule names

4. **Present findings clearly**: Organize results by:

- Severity (errors first, then warnings)

- File location with `file_path:line_number` format

- Specific rule violated

- Suggested fix when available

5. **Offer to fix issues**: After presenting findings:

- Group similar issues that can be batch-fixed

- Apply auto-fixable corrections if user approves

- Explain manual fixes needed for complex issues

Example Usage

**User**: "Check this code for linting errors"

**Assistant**:

```

Let me run ESLint to check for code quality issues.

[Runs: npx @eslint/mcp]

Found 3 issues:

Errors:

Warnings:

Would you like me to fix these issues?

```

Constraints

Additional Notes