batch-lint-cleanup

Analyze ESLint violations and fix specific rules in isolation.

1|1|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/ag-grid/ag-shared --skill batch-lint-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch-lint-cleanup
Source: https://github.com/ag-grid/ag-shared/tree/main/prompts/skills/batch-lint-cleanup
Command: npx skills add https://github.com/ag-grid/ag-shared --skill batch-lint-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze ESLint violations and auto-fix specific rules in isolation to enable safe, reviewable lint cleanup.

Core Features & Use Cases

  • Isolate and audit ESLint violations by rule with clear top-violations reports.
  • Auto-fix eligible rules while ensuring changes stay isolated for easy review.
  • Guided workflows to validate fixes and maintain codebase integrity.

Quick Start

Run the lint tool in report mode to view top ESLint violations, then fix a specific rule in isolation.

Frequently Asked Questions about batch-lint-cleanup

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

FAQPage Schema
How do I auto-fix ESLint violations without creating an unreviewable mess?

Isolating ESLint auto-fixes by specific rule names allows deterministic, isolated runs. This approach provides clear audit trails and verification steps, ensuring changes remain reviewable and maintain codebase integrity during cleanup.

How do I find the most frequent ESLint violations in my project?

You can analyze your project's ESLint output in report mode to surface the most frequent issues. Running the tool with no arguments generates a top-violations report, helping you prioritize which rules to address first during lint cleanup.

What is the best way to apply ESLint auto-fixes rule by rule?

The best way to apply ESLint auto-fixes rule by rule is by passing a specific rule name to the tool. This triggers an isolated run that fixes only eligible violations for that rule, ensuring changes are deterministic and easy to review.

Can I validate ESLint auto-fixes before committing them to my codebase?

Yes, the workflow includes guided validation steps to verify fixes after they are applied. By ensuring that auto-fixes stay isolated to individual rules, you can safely review the specific changes and validate codebase integrity before committing.

Does isolating ESLint fixes by rule help with code review?

Yes, isolating ESLint fixes by rule directly supports code review by ensuring changes stay isolated. This deterministic approach generates clear audit trails and verification steps, making it easier to review specific auto-fixes without unrelated code changes.