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
- microsoft/coreai-design-systemtheir own version, first seen Nov 15, 2026
- jakubtobiasz/second-brain-templatetheir own version, first seen Nov 15, 2026
- wikilayer/skillstheir own version, first seen Nov 13, 2026
- playingpossumm/loose-endstheir own version, first seen Nov 10, 2026
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
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.
ArtemXTechSkillquery
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
JaimeGBASkillingest
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
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 5 projects that use this
PydanticSkillcoverage
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
seongjaeryuSkillsave
Complete and save your current thinking to Bindly
Also in 5 projects that use this
GitHubSkillstate-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
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- ray-project/ray★ 44ksame name
- FalkorDB/FalkorDB★ 11ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- aaddrick/claude-desktop-debian★ 5.5ksame name
- cloudposse/atmos★ 1.4ksame name
- ethereum/execution-specs★ 1.2ksame name
- adobe/S3Mock★ 1.2ksame name
- maxGraph/maxGraph★ 1.2ksame name
- jason-effi-lab/karpathy-llm-wiki-vault★ 718same name
72 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bump-versionSkill
- community-triageSkill
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
- Distinctive: line 11
Run all project linters and resolve every issue.
- Distinctive: line 15
Use the repository's selected or activated virtual environment for every linter invocation.
- Very specific: line 20
Run Ruff and Pyright as modules through <venv-python> rather than using system-level commands.
- Distinctive: line 27
Run the linters in this order each iteration:
- Distinctive: line 47
Max 5 iterations: If issues persist after 5 loops, stop and report the remaining errors to the user.
- Very specific: line 49
Use
ruff check . --fixbefore manual fixes: Never manually fix what ruff can auto-fix. - Distinctive: line 50
Minimal changes: Only touch lines the linters flag.
- Distinctive: line 52
Report clearly: After each iteration, briefly state which linter you ran and how many errors remain.
- Very specific: line 53
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 …
“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.
Files
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:
- Ruff auto-fix —
<venv-python> -m ruff check . --fix(safe, auto-fixable issues) - Ruff check —
<venv-python> -m ruff check .(remaining issues that need manual fixes) - 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, breakRules
- 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 . --fixbefore 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
Anytype 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
$ARGUMENTScontains a file path or glob, pass it to both linters to scope the run (e.g.,<venv-python> -m ruff check $ARGUMENTSand<venv-python> -m pyright --pythonpath <venv-python> $ARGUMENTS).
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
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.

