lint-check
Skill0 starsChanged 8 months agoMITView on GitHub
Run ruff, mypy, format check, and pip-audit
2 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/fluentuitheir own version, first seen Oct 5, 2026
- timothywarner-org/agent-security-quorumtheir own version, first seen Mar 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- microsoft/fluentui★ 20ksame name
- timothywarner-org/agent-security-quorum★ 2same name
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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs-updateSkill
- spec-compileSkill
- spec-createSkill
- spec-testSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the full quality gate: linting, formatting, type checking, and vulnerability audit.
- Distinctive: line 15
Run these commands sequentially in the project root:
- Distinctive: line 37
If FAIL: summary of issues found
- Distinctive: line 41
Run ALL checks even if earlier ones fail
- Distinctive: line 42
Do NOT auto-fix issues — report them for manual resolution
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
lint-check
Run the full quality gate: linting, formatting, type checking, and vulnerability audit.
Usage
/lint-check
Process
Run these commands sequentially in the project root:
cd /c/Users/iatiq/Documents/dev/personal/health_app/graphcrew
# 1. Ruff lint check
uv run ruff check src/ tests/
# 2. Ruff format check (no changes)
uv run ruff format --check src/ tests/
# 3. mypy type check
uv run mypy src/graphcrew/ tests/
# 4. pip-audit vulnerability scan
uv run pip-auditReport
For each check, report:
- PASS or FAIL
- If FAIL: summary of issues found
- Total: X/4 checks passed
Rules
- Run ALL checks even if earlier ones fail
- Do NOT auto-fix issues — report them for manual resolution
- ruff
--fixcan make semantic changes, so never run it automatically
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.

