lint-fixer

yamadashy's avatarfrom yamadashy

Use this skill to run npm run lint and fix linting issues. Triggers on fixing lint errors after code changes or validating code against project style guidelines.

⭐21.0kstars🔀963forks📁View on GitHub🕐Updated Jan 4, 2026
[Code Review]

When & Why to Use This Skill

The Lint Fixer skill is a comprehensive developer tool designed to automate code quality enforcement and style consistency. By integrating high-performance tools like Biome, oxlint, and TypeScript type-checking, it identifies and automatically resolves formatting issues, syntax errors, and project-specific style violations. This skill ensures that code remains clean, maintainable, and secure by also scanning for exposed secrets, significantly reducing the manual effort required during the code review process.

Use Cases

  • Automated Style Correction: Instantly fix formatting and linting issues using Biome and oxlint after major code changes to ensure adherence to project style guides.
  • Pre-Commit Security Scanning: Utilize secretlint to detect and prevent the accidental commitment of sensitive credentials or API keys to the repository.
  • Static Type Verification: Run TypeScript checks (tsgo) to identify potential type mismatches and logic errors without executing the code.
  • Codebase Standardization: Rapidly update legacy files to meet modern configuration standards (e.g., 120-character line limits, single quotes) across large projects.
namelint-fixer
description"Use this skill to run npm run lint and fix linting issues. Triggers on fixing lint errors after code changes or validating code against project style guidelines."

Lint Fixer

Fix linting issues while preserving code functionality.

Lint Tools

npm run lint runs 4 tools in sequence:

  1. Biome (biome check --write) - Formatter + linter, auto-fixes
  2. oxlint (oxlint --fix) - Fast JS/TS linter, auto-fixes
  3. tsgo (tsgo --noEmit) - TypeScript type checking
  4. secretlint - Detects secrets/credentials

Workflow

  1. Run npm run lint to identify issues
  2. Review errors by category (type errors vs style vs secrets)
  3. Fix issues - Biome/oxlint auto-fix most style issues
  4. Run npm run lint again to verify
  5. Run npm run test to ensure no breakage

Config Files

  • biome.json - Formatting rules (2 spaces, 120 chars, single quotes)
  • .oxlintrc.json - JS/TS lint rules
  • .secretlintrc.json - Secret detection rules

Key Points

  • Biome/oxlint auto-fix most issues; review changes
  • Type errors (tsgo) require manual fixes
  • Never change code behavior when fixing lint
  • Keep files under 250 lines