lint-fix

Detects project linting tools, builds a validation pipeline, and fixes errors atomically.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill lint-fix-siegenthalerroger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-fix
Source: https://github.com/siegenthalerroger/.llmctl-marketplace/tree/main/plugins/llmctl-workflow-0.2.1/skills/lint-fix
Command: npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill lint-fix-siegenthalerroger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually discovering and running every linter, formatter, type checker, and test suite in a project is error-prone, and fixing many lint errors at once often introduces new failures. This Skill automates tool detection, pipeline ordering, and one-at-a-time verified fixes so the codebase reaches zero validation errors without cascade breakage. ## Core Features & Use Cases - Automatic tool detection: Scans Makefile targets, package.json scripts, go.mod, pyproject.toml, .csproj, Cargo.toml, and standalone linter configs to find available linters, formatters, and test runners. - Ordered validation pipeline: Arranges generation, formatting, linting, type checking, validation, testing, and building in the correct sequence, running code generation first so generated output does not overwrite manual fixes. - Atomic fix protocol: Fixes exactly one issue at a time, re-runs the failing command after each fix, and reverts any change that introduces new errors. - Use Case: Before committing a Go project, run the Skill to detect golangci-lint, gofmt, go vet, and go test, execute them in order, and fix each reported issue until the full pipeline passes end-to-end. ## Quick Start Ask the assistant to detect all linting and validation tools in this project, run the full pipeline, and fix every error until everything passes.

Frequently Asked Questions about lint-fix

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

FAQPage Schema
How do I fix all linting errors in a project automatically?▼

Detect the project's linters from its Makefile, package.json, go.mod, or pyproject.toml, run them in an ordered pipeline, then fix issues one at a time. Re-run the failing command after each fix to confirm no new errors were introduced.

How to run linters and formatters in the correct order?▼

Run code generation first, then formatters, then linters, type checkers, validation, tests, and builds last. Generation must come first because generated code can overwrite manual fixes made earlier in the pipeline.

Which linting tools does this pipeline detect?▼

It detects Makefile targets, package.json scripts, golangci-lint, gofmt, go vet, ruff, black, flake8, mypy, pytest, dotnet format, cargo clippy, rustfmt, eslint, prettier, biome, and markdownlint based on project config files.

What happens if no linting tools are found in my project?▼

The pipeline stops and reports that no linting or validation tools were detected, listing what was checked. It then offers to help set up linting for the project instead of running an empty pipeline.

Why fix lint errors one at a time instead of in batches?▼

Batch fixes can introduce new errors that are hard to trace back to a specific change. Fixing one issue and immediately re-running the failing command catches regressions instantly and allows reverting a bad fix with git.

What should I do when a lint fix creates new errors?▼

Revert the change with git checkout or git stash, then try a different fix for the same issue. If fixes become circular or require architectural changes, document the issue and suppress the rule with a justification comment as a last resort.