lint-fixer

Automate linting and fixes for JavaScript/TypeScript projects using Biome, oxlint, tsgo, and secretlint.

Updated Jul 15, 2023
One-click install
npx skills add https://github.com/algusaem/algusaem-portfolio --skill lint-fixer-algusaem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fixer
Source: https://github.com/algusaem/algusaem-portfolio/tree/main/.claude/skills/lint-fixer
Command: npx skills add https://github.com/algusaem/algusaem-portfolio --skill lint-fixer-algusaem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates linting and fixes for codebases, helping teams maintain consistent style and reduce manual debugging time.

Core Features & Use Cases

  • Automated lint checks: Runs the project's lint suite and applies safe, auto-generated fixes.
  • Multi-tool integration: Coordinates Biome, oxlint, tsgo, and secretlint to cover formatting, type checking, and secret detection.
  • Use Case: Run this as part of a pre-commit hook or CI pipeline to ensure every change conforms to project standards and to surface potential security risks.

Quick Start

Run npm run lint to identify and fix lint issues. Review changes, then run npm run lint again to verify. Finally, run npm run test to ensure 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 auto-fix lint issues in a JavaScript or TypeScript project?

You can auto-fix lint issues by running npm run lint to apply safe, auto-generated fixes for style and type errors. Review the changes, run npm run lint again to verify, then execute npm run test to ensure no regressions.

Can I run secret detection and type checks alongside formatting in my CI pipeline?

Yes, you can coordinate secret detection, type checks, and formatting within your CI pipeline. The workflow integrates Biome, oxlint, tsgo, and secretlint to surface security risks and enforce project standards on every change.

Do I need Node.js and npm to run automated linting and fixes?

Yes, Node.js and npm are required to run the automated linting and fixes. The process executes within your development environment or CI workflows using the project's configured linting tools.

What is the best way to ensure my pre-commit hook catches both style issues and potential secrets?

The best way to catch style issues and secrets is running an automated lint suite as a pre-commit hook. This coordinates multiple tools to apply safe fixes and detect security risks before changes are committed.

Why does my lint fix process require running tests afterward?

Running tests after lint fixing is required to ensure no regressions. While the applied fixes are designated as safe, executing your test suite verifies that the automated style and type adjustments do not break existing functionality.