lint-fix

Detect linting and validation failures and fix them atomically across project toolchains.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill lint-fix-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fix
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/lint-fix
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill lint-fix-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detect project linting and validation failures, build an ordered execution pipeline across detected tools, and fix issues atomically so the repository reaches a clean, zero-error state before commits or releases.

Core Features & Use Cases

  • Automatic tool detection: Scans Makefile targets, package.json scripts, go.mod, pyproject.toml, Cargo.toml, and common linter configs to discover available formatters, linters, type checkers, tests, and build steps.
  • Ordered validation pipeline: Runs generation, formatting, linting, type checking, validation, testing, and build steps in an optimal sequence and presents the pipeline for user approval.
  • Atomic fix protocol: Fixes one reported issue at a time, re-verifies the offending command, reverts unsafe changes, and continues only after each fix is verified to avoid cascading failures.
  • Use case: Prepare a pull request by ensuring all linters, formatters, and tests pass in sequence and automatically applying safe fixes where available.

Quick Start

Run the lint-fix skill to detect all validation tools, build a recommended pipeline, and iteratively fix reported issues until every tool reports zero errors.

Frequently Asked Questions about lint-fix

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

FAQPage Schema
How do I automate linting and validation fixes across multiple project toolchains?

Automate linting by scanning repository artifacts like Makefile, package.json, and pyproject.toml to detect available tools, build an ordered validation pipeline, and apply atomic fixes until the project reaches a zero-error state.

What is the best way to ensure formatters and type checks pass before a pull request?

Run an ordered validation pipeline that executes generation, formatting, linting, type checking, and testing in sequence, applying atomic single-issue fixes with immediate verification to ensure all validation steps pass.

Does this automated linting approach work with Go, Python, and Rust repositories?

Yes, the tool detection mechanism scans go.mod, pyproject.toml, Cargo.toml, package.json, Makefile, and .NET artifacts to automatically discover and run the appropriate formatters, linters, and build steps for those environments.

Why does my automated validation pipeline fail after fixing the first linting issue?

Cascading failures occur when multiple fixes are applied at once. An atomic fix protocol resolves this by fixing one issue at a time, reverting unsafe changes, and re-verifying the offending command before proceeding to the next.

Do I need to manually configure linters to use the atomic fix protocol?

No manual configuration is required. The tool automatically detects installed linting and validation tools from your project configuration files and generates the optimal execution sequence for you to approve.

What happens if an automatically applied lint fix breaks the build?

Unsafe changes are immediately reverted by the atomic fix protocol. The system verifies each fix against the offending command and reverts failures before continuing, concluding with a final end-to-end validation pass.