lint-fixer

Fix lint issues in JavaScript/TypeScript projects using npm scripts.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mwathiben/PropManager --skill lint-fixer-mwathiben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fixer
Source: https://github.com/mwathiben/PropManager/tree/main/.claude/skills/lint-fixer
Command: npx skills add https://github.com/mwathiben/PropManager --skill lint-fixer-mwathiben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of enforcing code quality by automatically detecting and fixing lint issues across a project, reducing manual debugging time.

Core Features & Use Cases

  • Automated linting: Run Biome, oxlint, tsgo, and secretlint in sequence to clean up code and catch issues early.
  • Quality gates: Ensure style consistency and catch real errors before they reach CI.
  • Use Case: A team integrates linting into pre-commit hooks and CI pipelines to maintain consistent coding standards.

Quick Start

Run npm run lint to identify and fix lint issues, then npm run test to verify no regressions.

Frequently Asked Questions about lint-fixer

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

FAQPage Schema
How do I automatically fix lint issues in a JavaScript or TypeScript project?

To automatically fix lint issues, run npm run lint to execute configured linters like Biome and oxlint, then run npm run test to verify no regressions were introduced.

Do I need specific configuration files to automate linting in CI pipelines?

Yes, automating linting requires configuration files biome.json, .oxlintrc.json, and .secretlintrc.json, alongside npm scripts named lint and test in your project.

What's the best way to catch secret leaks and style issues before pre-commit?

The best way to catch leaks and style issues pre-commit is running secretlint alongside Biome and oxlint sequentially to clean code and enforce quality gates before CI.

How does sequential linting with multiple tools maintain code quality?

Sequential linting maintains code quality by running Biome, oxlint, tsgo, and secretlint in order to automatically detect and fix issues, reducing manual debugging time.

Can I use this automated linting workflow without a local npm development environment?

No, this automated linting workflow requires a local development environment using npm, specifically needing npm scripts named lint and test to execute the linter sequence.