agentleFS
yu-iskwyu-iskw/skill-inspector/.claude/skills/lint-and-fix/SKILL.md

lint-and-fix

Skill2 starsChanged 10 months agoApache-2.0View on GitHub

Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Format: Run pnpm format (which executes trunk fmt) to automatically fix trivial formatting issues.

    line 14
  2. Very specific:

    Identify: Run pnpm lint (which executes trunk check) to list any remaining violations.

    line 15
  3. Very specific:

    If pnpm lint passes: Finish.

    line 19
  4. Distinctive:

    If it fails: Analyze the new failure and repeat the loop.

    line 20
  5. Very specific:

    No more errors reported by pnpm lint.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 4 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

Lint and Fix Loop: Trunk

Purpose

An autonomous loop for the agent to identify, fix, and verify linting and formatting violations using Trunk.

Loop Logic

  1. Format: Run pnpm format (which executes trunk fmt) to automatically fix trivial formatting issues.
  2. Identify: Run pnpm lint (which executes trunk check) to list any remaining violations.
  3. Analyze: Examine the output from Trunk, focusing on the file path, line number, and error message. Refer to ../common-references/troubleshooting.md for environment or runtime issues.
  4. Fix: Apply the minimum necessary change to the source code to resolve the reported linting violations.
  5. Verify: Re-run the loop (starting from Format) until all issues are resolved.
    • If pnpm lint passes: Finish.
    • If it fails: Analyze the new failure and repeat the loop.

Termination Criteria

  • No more errors reported by pnpm lint.
  • Reached max iteration limit (default: 5).

Examples

Scenario: Fixing violations in a modified file

  1. Agent runs pnpm format to ensure consistent style.
  2. Agent runs pnpm lint and finds a linting violation in src/index.ts.
  3. Agent analyzes the error and applies a manual fix.
  4. Agent runs pnpm format again (part of the loop).
  5. Agent runs pnpm lint and it now passes.

Resources

  • Trunk CLI Reference: Common commands for linting and formatting.
  • Trunk Documentation: Official documentation for the Trunk CLI.

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.