lint-fix

Name: lint-fix
Availability: InStock
Author: alexanderjamesmcleod

Automate linting, auto-fixing, type checking, and formatting for JavaScript/TypeScript projects.

Updated Aug 23, 2026

Search Tags:#linting #bash #tooling #auto-fix #code-quality #lint

Ready to run

npx skills add https://github.com/alexanderjamesmcleod/makecents --skill lint-fix

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires biome, eslint, prettier, typescript, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Code quality and consistency often lag behind during development, leading to bugs and brittle codebases. This skill automates linting, formatting, and type checks to keep your project clean and compliant.

Core Features & Use Cases

Linting and auto-fixing for style and potential errors across the codebase.
Type checking to catch type errors during development.
Code formatting to enforce consistent style.
Use Case: Integrate into CI to ensure every commit passes lint, format, and type checks.

Quick Start

Run lint-fix to lint and auto-fix code across your project.

Frequently Asked Questions about lint-fix

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

FAQPage Schema

How do I automate linting and auto-fix code across a JavaScript project?▼

Automate linting and auto-fix code by running a script that leverages local tooling like eslint or biome to detect style violations and potential errors, applying automated fixes across the codebase to maintain code quality.

What's the best way to enforce code formatting and type checks in a TypeScript project?▼

Enforce code formatting and type checks in a TypeScript project by integrating prettier and a TypeScript configuration (tsconfig.json) into your workflow, ensuring consistent style and catching type errors during development.

Do I need a tsconfig.json file to run linting and formatting checks?▼

Yes, a tsconfig.json file is required to run linting and formatting checks correctly, as the TypeScript configuration provides the necessary environment for type checking and auto-fixing workflows.

Can I integrate auto-fix linting and type checks into CI pipelines?▼

Yes, you can integrate auto-fix linting and type checks into CI pipelines to ensure every commit passes lint, format, and type checks, preventing bugs and brittle codebases from being merged.

Does this linting workflow support both eslint and biome for code quality checks?▼

Yes, this linting workflow supports both eslint and biome, allowing you to apply linting, auto-fixing, and code formatting using your preferred local tooling for JavaScript and TypeScript projects.

Why should I automate code quality checks instead of running them manually?▼

Automating code quality checks prevents consistency from lagging behind during development, systematically catching style violations and type errors that manual checks miss, keeping your project clean and compliant.