sfermanelli-fix-lint

Fix linting and TypeScript errors across a codebase automatically.

1|Updated Mar 19, 2026

Search Tags:#typescript #eslint #autofix #code-quality #static-analysis #lint

Ready to run

npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-fix-lint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sfermanelli-fix-lint
Source: https://github.com/sebafermanelli/sfermanelli-skills/tree/main/sfermanelli-fix-lint
Command: npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-fix-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the cleanup of linting and TypeScript errors across a codebase, reducing manual debugging time and preventing regressions.

Core Features & Use Cases

Automated lint fixes: Apply consistent fixes for eslint rules and formatting.
Type-check error resolution: Detect and repair type errors, incorrect generics, and missing typings.
Use Case: When CI fails due to lint or type errors, trigger this skill to repair issues and re-run checks.

Quick Start

Run linting and type-checking across the repository, then let the auto-fix workflow repair issues and re-run checks.

Frequently Asked Questions about sfermanelli-fix-lint

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

FAQPage Schema

How do I automatically fix ESLint and TypeScript errors across a codebase?▼

Automated lint fixes apply consistent corrections for eslint rules and formatting across a project. This reduces manual debugging time by resolving errors programmatically rather than editing files individually.

Can I use an automated linter to repair CI pipeline failures caused by type errors?▼

Yes, when CI fails due to lint or type errors, an automated repair workflow can detect incorrect generics, apply fixes, and re-run checks to satisfy pipeline requirements across multiple packages.

How does static analysis detect and repair TypeScript type-check errors?▼

Static analysis identifies type errors by evaluating TypeScript code against defined rules. An automated fixer then repairs incorrect generics and missing typings before re-running validation checks.

What is the best way to handle linting and type errors across multiple packages?▼

The best way to handle errors across multiple packages is to run linting and type-checking across the entire repository, apply automated fixes, and validate results to ensure no regressions occur.

Does automated lint fixing work with existing ESLint configurations?▼

Automated lint fixing works with existing ESLint configurations by applying consistent fixes for your current eslint rules and formatting, then validating the results to prevent regressions.