format-and-lint

Fixes linting and formatting issues across a project using npm lint and Biome.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill format-and-lint-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: format-and-lint
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/format-and-lint
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill format-and-lint-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lint errors and inconsistent formatting block commits and CI pipelines, and fixing them manually one file at a time is slow and error-prone. This Skill provides a disciplined workflow to discover, auto-fix, and manually resolve every remaining issue until the project passes cleanly. ## Core Features & Use Cases - Systematic Issue Discovery: Runs npm run lint and npm run lint --fix to auto-resolve fixable issues, then reads remaining errors with the read_lints tool. - Safe Manual Fixes: Enforces strict rules such as never using any to bypass type errors and never adding lint-disable comments when a proper fix exists. - Biome Formatting Compliance: Applies project Biome rules (2-space indent, double quotes, semicolons) via npm run check:fix or npm run format. - Use Case: Before opening a pull request, run this Skill to iterate through all lint errors file by file, verify each fix, and confirm npm run lint exits with code 0. ## Quick Start Fix all linting and formatting issues in this project and confirm the lint command passes with zero errors.

Frequently Asked Questions about format-and-lint

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

FAQPage Schema
How do I fix all lint errors in a TypeScript project?▼

Run npm run lint to list issues, then npm run lint --fix for automatic fixes. Read remaining errors with the read_lints tool, fix each file manually with proper typing, and re-run lint until it exits with code 0.

How to auto-fix formatting issues with Biome?▼

Use npm run check:fix or npm run format to apply Biome formatting rules such as 2-space indentation, double quotes, and semicolons. Biome handles safe automatic fixes, while remaining lint errors require manual correction.

Why should I avoid using any to fix TypeScript lint errors?▼

Using any bypasses the type checker and hides real type mismatches that can cause runtime bugs. The correct approach is to type the value properly so the error is resolved rather than suppressed.

When should I not add a lint-disable comment?▼

Avoid lint-disable comments whenever a genuine fix exists, such as correcting import order or resolving a type issue. Suppression comments accumulate technical debt and hide problems from future contributors and CI checks.

How do I verify lint fixes before committing code?▼

After fixing each file, re-check it with the read_lints tool to confirm the errors are gone. Finally, run npm run lint one more time and confirm it exits with code 0 and no unsafe fixes were introduced.