agentleFS
diriendirien/yet-another-agent-harness/.claude/skills/lint-fix/SKILL.md

lint-fix

Skill19 starsChanged 8 months agoMITView on GitHub

Detect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docstring, changelog and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    docstring

    Write or review docstrings for public modules, classes, and functions in sdm/. Use when adding or reviewing docstrings to follow repo best practices (Args sections, paper citations, tensor shape notation).

    Also in 3 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 5 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no tools are detected, report to the user and offer to help set up linting.

    line 46
  2. Very specific:

    If make gen, make generate, or an equivalent code generation command is detected, run it before any linting.

    line 51
  3. Distinctive:

    If generation fails, stop and fix the generation issue before proceeding to linting.

    line 60
  4. Distinctive:

    If the user wants to add, remove, or reorder commands, adjust the pipeline accordingly.

    line 89
  5. Distinctive:

    Run each command in order.

    line 94
  6. Distinctive:

    Verify: the issue is resolved AND no new issues appeared

    line 122
  7. Distinctive:

    If fix created new issues: revert and try a different approach

    line 123
  8. Distinctive:

    If fix is clean: move to the next issue

    line 124
  9. Distinctive:

    After all issues for the failing command are resolved, continue the pipeline from the next command.

    line 126
  10. Distinctive:

    After all commands pass individually, run the full pipeline end-to-end as a single sequence:

    line 134
  11. Distinctive:

    All commands must pass in sequence.

    line 141
  12. Very specific:

    Formatting issues: run the formatter with --write or -w flag instead of --check.

    line 161
  13. Very specific:

    Check for --fix flags.

    line 165
  14. Distinctive:

    Read the error carefully and fix the root cause.

    line 171

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. --><!-- SPDX-License-Identifier: Apache-2.0 -->

Lint and Validation Pipeline

Detect all linting, formatting, and validation tools in the project, build an ordered execution pipeline, run everything to zero errors, and fix issues atomically.

Step 1: Detect project tools

Scan the project root for configuration files, Makefile targets, and package manager scripts to identify available tools.

Check in order:

  1. Makefile — discover targets: lint, test, validate, format, gen, build, check, vet
  2. package.json — discover scripts: lint, test, format, prettier, eslint, build, typecheck
  3. go.mod — check for golangci-lint, gofmt, go vet, go test
  4. pyproject.toml / setup.py — check for ruff, black, flake8, mypy, pytest
  5. .csproj / .sln — check for dotnet format, build, test
  6. Cargo.toml — check for cargo clippy, fmt, test
  7. Standalone configs — .eslintrc*, .prettierrc*, biome.json, .golangci.yml, .markdownlint*

For detailed detection commands per ecosystem, see references/tool-detection.md.

If no tools are detected, report to the user and offer to help set up linting. Do not proceed with an empty pipeline.

Step 2: Check for code generation

If make gen, make generate, or an equivalent code generation command is detected, run it before any linting.

Generated code can overwrite manual fixes. Always generate first.

make gen 2>&1

If generation fails, stop and fix the generation issue before proceeding to linting.

Step 3: Build ordered pipeline

Arrange detected tools in execution order:

  1. Generation (make gen, code generators)
  2. Formatting (prettier, black, gofmt, rustfmt, dotnet format)
  3. Linting (eslint, golangci-lint, ruff, clippy, markdownlint)
  4. Type checking (tsc --noEmit, mypy)
  5. Validation (make validate, schema checks)
  6. Testing (go test, pytest, jest, cargo test, dotnet test)
  7. Building (go build, cargo build, dotnet build)

Present the detected pipeline to the user before executing:

Detected validation pipeline:
  1. make gen
  2. gofmt -s -l .
  3. golangci-lint run
  4. markdownlint '**/*.md'
  5. go test ./...
  6. go build ./...

Proceed? (y/n)

If the user wants to add, remove, or reorder commands, adjust the pipeline accordingly.

Step 4: Execute pipeline

Run each command in order. Stop at the first failure.

# Run each command, stop on failure
for cmd in "${PIPELINE[@]}"; do
    echo "Running: $cmd"
    eval "$cmd" 2>&1
    if [ $? -ne 0 ]; then
        echo "FAILED: $cmd"
        # Proceed to atomic fix protocol for this command
        break
    fi
    echo "PASSED: $cmd"
done

Capture the full output of the failing command — file paths, line numbers, rule names, and error messages are needed for fixing.

Step 5: Atomic fix protocol

Fix issues from the failing command one at a time. This prevents cascade failures where fixing one issue introduces others.

For each issue:

  1. Fix exactly ONE issue (minimal change)
  2. Re-run the failing command immediately
  3. Verify: the issue is resolved AND no new issues appeared
  4. If fix created new issues: revert and try a different approach
  5. If fix is clean: move to the next issue

After all issues for the failing command are resolved, continue the pipeline from the next command.

For detailed protocol, rollback strategies, and edge cases, see references/fix-protocol.md.

Step 6: Final verification

After all commands pass individually, run the full pipeline end-to-end as a single sequence:

cmd1 && cmd2 && cmd3 && ... && echo "PASS" || echo "FAIL"

All commands must pass in sequence. If any command fails in the final run, return to Step 5 for that command.

Present the final result:

Validation pipeline: ALL PASSED

  1. make gen           PASS
  2. gofmt -s -l .      PASS
  3. golangci-lint run   PASS
  4. markdownlint        PASS
  5. go test ./...       PASS
  6. go build ./...      PASS

Zero errors across all validation tools.

Common fix patterns

Formatting issues: run the formatter with --write or -w flag instead of --check. Most formatters have an auto-fix mode.

Import ordering: most linters have auto-fix for import sorting. Check for --fix flags.

Trailing whitespace / EOF newlines: fix with editor settings or sed -i 's/[[:space:]]*$//' file.

Type errors: these usually require code changes, not auto-fix. Read the error carefully and fix the root cause.

Test failures: investigate the failure — is it a real bug introduced by your changes, or a pre-existing flaky test?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.