ESLint Baseline Hardening
Raises ESLint quality in bounded steps by reviewing current rules, warnings, TypeScript and framework-specific checks, and CI integration without turning the repo into a massive lint refactor.
SKILL.mdskills/quality/eslint/eslint-baseline-hardening/SKILL.md
GitHubESLint Baseline Hardening
Purpose
Use this skill to harden ESLint in small, safe steps.
The goal is to improve the lint baseline without causing a repo-wide breakage or mixing lint cleanup with unrelated refactors.
The core rule is simple:
Raise the standard in phases.
When to Use
Use this skill when:
- the repo has too many warnings ignored
- lint rules need a phased rollout
- CI should enforce a stronger baseline
- TypeScript or framework-specific linting needs review
Do
Review:
- active rules
- disabled rules
- warnings versus errors
- TypeScript rules
- framework-specific rules
- CI integration
Change the baseline in bounded increments and validate each step.
Do Not
Avoid broad lint churn without a plan.
Avoid changing rules and formatting and logic in the same hop.
Avoid forcing a strict baseline before the repo is ready.
Review Checklist
- Current lint state is understood.
- Errors and warnings are classified.
- CI integration is considered.
- The change is bounded and safe.
Expected Output
- Inspect the lint baseline.
- Classify rule gaps.
- Propose phased hardening.
- Keep the change bounded.
- Validate with the project checks.