agentleFS
roryeckelroryeckel/wyoming_openai/.agents/skills/lint/SKILL.md

lint

Skill226 starsChanged 29 days agoApache-2.0View on GitHub

Run all linters (ruff, pyright) and fix issues in a loop until the codebase is clean.

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 10 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 18 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 27 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 5 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

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 6

    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:

    Run all project linters and resolve every issue.

    line 11
  2. Distinctive:

    Use the repository's selected or activated virtual environment for every linter invocation.

    line 15
  3. Very specific:

    Run Ruff and Pyright as modules through <venv-python> rather than using system-level commands.

    line 20
  4. Distinctive:

    Run the linters in this order each iteration:

    line 27
  5. Distinctive:

    Max 5 iterations: If issues persist after 5 loops, stop and report the remaining errors to the user.

    line 47
  6. Very specific:

    Use ruff check . --fix before manual fixes: Never manually fix what ruff can auto-fix.

    line 49
  7. Distinctive:

    Minimal changes: Only touch lines the linters flag.

    line 50
  8. Distinctive:

    Report clearly: After each iteration, briefly state which linter you ran and how many errors remain.

    line 52
  9. Very specific:

    If $ARGUMENTS contains a file path or glob, pass it to both linters to scope the run (e.g., <venv-python> -m ruff check $ARGUMENTS and …

    line 53

“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

Current State

  • Branch: !git branch --show-current
  • Dirty files: !git diff --name-only

Run all project linters and resolve every issue. Loop until the codebase passes cleanly.

Python environment

Use the repository's selected or activated virtual environment for every linter invocation. Do not assume a particular environment name or location. Resolve the interpreter from the active environment (for example, with python -c "import sys; print(sys.executable)") and refer to it below as <venv-python>.

Run Ruff and Pyright as modules through <venv-python> rather than using system-level commands. Pass the same interpreter to Pyright with --pythonpath so its import resolution uses the environment containing the project's dependencies. If no project environment is selected, stop and report that linting requires the development environment to be activated or selected.

Linter pipeline

Run the linters in this order each iteration:

  1. Ruff auto-fix — <venv-python> -m ruff check . --fix (safe, auto-fixable issues)
  2. Ruff check — <venv-python> -m ruff check . (remaining issues that need manual fixes)
  3. Pyright — <venv-python> -m pyright --pythonpath <venv-python> (type-checking)

Resolution loop

while linters report errors:
    1. Run <venv-python> -m ruff check . --fix  (let ruff auto-fix what it can)
    2. Run <venv-python> -m ruff check .
       - If errors remain, read the offending files and fix them
    3. Run <venv-python> -m pyright --pythonpath <venv-python>
       - If errors remain, read the offending files and fix them
    4. If no errors in steps 2 and 3, break

Rules

  • Max 5 iterations. If issues persist after 5 loops, stop and report the remaining errors to the user.
  • Ruff first, pyright second. Ruff fixes (especially import sorting) can eliminate pyright false positives, so always run ruff before pyright.
  • Use ruff check . --fix before manual fixes. Never manually fix what ruff can auto-fix.
  • Minimal changes. Only touch lines the linters flag. Do not refactor, add docstrings, or "improve" surrounding code.
  • Preserve behavior. Fixes must not change runtime behavior. If a fix requires a judgment call (e.g., an Any type that needs a real annotation), prefer the narrowest correct type.
  • Report clearly. After each iteration, briefly state which linter you ran and how many errors remain. When done, summarize what was fixed.
  • If $ARGUMENTS contains a file path or glob, pass it to both linters to scope the run (e.g., <venv-python> -m ruff check $ARGUMENTS and <venv-python> -m pyright --pythonpath <venv-python> $ARGUMENTS).

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.