eslint-checker

The eslint-checker skill is a specialized agent workflow designed to automate the maintenance of code quality and style standards in JavaScript and TypeScript environments. It acts as a primary interface for running static analysis, ensuring that project-specific linting configurations are respected, and providing a controlled mechanism for auto-fixing code violations without risking production stability. By integrating directly with existing ESLint configurations like eslint.config.js or .eslintrc, the agent bridges the gap between manual CLI execution and automated code health management.

• Executes full-suite static analysis across source directories with support for specific file extensions like .js, .ts, and .tsx.

• Implements a grounding checkpoint system that verifies Node.js, npm, ESLint installation, and configuration files prior to execution.

• Performs dry-run fixes to preview changes before applying automatic corrections, mitigating the risk of unintended code transformations.

• Generates structured diagnostic reports in JSON, HTML, or compact formats for deep inspection of rule violations and error counts.

• Uses an uncertainty escalation protocol that prompts users for confirmation when encountering ambiguous configurations, custom rules, or conflicts with Prettier.

• Follows a recovery protocol for error handling, including parsing error diagnostics, plugin validation, and multi-attempt retry logic.

• Provides intelligent context scoping to ensure test files, build outputs, and node_modules are appropriately included or excluded based on user intent.

• Use this tool when you need to enforce consistent coding styles across a team or large codebase.

• Ideal for auditing existing projects for technical debt, specifically identifying unused variables or deprecated syntax.

• Input requirements include a valid JavaScript/TypeScript project structure; if configurations are missing, the agent guides the user in setting up templates.

• The tool outputs summarized markdown reports, detailed JSON diagnostic data, and applied diffs for any auto-fix operations.

• Constraints include strict avoidance of auto-fixing production code without explicit user verification and a requirement for a valid ESLint configuration environment.