agentleFS
Sign inStart free
lgtm-hqlgtm-hq/ai-skills/skills/lint/SKILL.md

lint

Skill1 starsChanged 11 days agoMITView on GitHub

Run linting and formatting. Prefer `uv run lintro chk` for checks and `uv run lintro fmt` for formatting when lintro is available; fall back to native tools only when lintro is unavailable or another skill documents a follow-up pass (e.g. raycast).

82 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use query, ingest and 9 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.
  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 17 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 26 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 5 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 4 projects that use this

  • AnthropicSkill

    digest

    Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 4

    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:

    Prefer lintro for linting and formatting.

    line 14
  2. Very specific:

    When available, use uv run lintro chk and uv run lintro fmt.

    line 15
  3. Distinctive:

    If lintro is unavailable, fall back to the language's native bundled tools (ruff, black, clippy, rustfmt, eslint, bandit, etc.).

    line 17
  4. Distinctive:

    When asked to lint or format code:

    line 52
  5. Very specific:

    Run uv run lintro fmt FIRST to auto-fix formatting issues across the ENTIRE codebase (when lintro is available)

    line 54
  6. Very specific:

    Run uv run lintro chk to check for remaining issues (when lintro is available)

    line 56
  7. Distinctive:

    If lintro is unavailable, use native tooling for the language and still aim for zero issues

    line 57
  8. Distinctive:

    Only as a last resort, add ignore comments WITH justification

    line 61

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

Tooling

Prefer lintro for linting and formatting. When available, use uv run lintro chk and uv run lintro fmt.

If lintro is unavailable, fall back to the language's native bundled tools (ruff, black, clippy, rustfmt, eslint, bandit, etc.). Another skill may document an additional pass after lintro (for example, raycast runs npm run lint after lintro — Raycast rules take precedence for extension-specific checks).

Commands

  • uv run lintro fmt — format code
  • uv run lintro chk — check code for issues
  • uv run lintro tst — run tests

Rules

  • CRITICAL: NEVER run lintro chk --tools ... (targeted/filtered checks). Always run the full uv run lintro chk without --tools. Filtered runs silently skip tools and miss issues.
    • Exception: single-tool runs (--tools <tool>) are permitted only when developing or verifying that specific lintro tool (the /lintro-add and /lintro-verify workflows). Even then, a full uv run lintro chk is still required before committing.
  • Linting must produce zero issues before proceeding
  • Fix ALL issues — whether introduced in the current session or pre-existing
  • Ignore policy — suppressing a finding is not a fix:
    1. Fix the root cause first. # noqa, # type: ignore, # nosec, # nosemgrep, # yamllint disable-line, etc. are a LAST resort, only when there is no reasonable fix.
    2. If suppression is genuinely required, use the narrowest possible ignore — specific rule code, single line — WITH an inline justification comment (# nosec B603 - fixed argv list, no shell). Unjustified ignores are rejected.
    3. Blanket or file-level ignores (whole-file disables, config-wide excludes) require a documented exception (e.g. in CONTRIBUTING.md).

Usage

When asked to lint or format code:

  1. Run uv run lintro fmt FIRST to auto-fix formatting issues across the ENTIRE codebase (when lintro is available)
  2. Run uv run lintro chk to check for remaining issues (when lintro is available)
  3. If lintro is unavailable, use native tooling for the language and still aim for zero issues
  4. Manually fix any issues found — do not leave issues unfixed
  5. Re-run the check command to verify all fixes
  6. Only as a last resort, add ignore comments WITH justification

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.

Check your setup, free