lint-fix
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Run formatting and linting via Makefile (make format, make lint).
18 other projects use a version of this.
Adopted by
Most recently taken up by
- khairold/claude-skillstheir own version, first seen Nov 16, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- allanninal/claude-code-skillstheir own version, first seen Oct 17, 2026
- chrisselig/claude-code-toolkittheir own version, first seen Oct 9, 2026
- llp-dev/claude-skillstheir own version, first seen Sep 9, 2026
- llp42/claude-skillstheir own version, first seen Sep 9, 2026
Used with
Projects with it also use docstring, changelog and 5 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.
NVIDIASkilldocstring
Write or review docstrings for public modules, classes, and functions in sdm/. Use when adding or reviewing docstrings to follow repo best practices (Args sections, paper citations, tensor shape notation).
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 5 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 5 projects that use this
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- getsentry/sentry★ 46ksame name
- dirien/yet-another-agent-harness★ 19same name
- jhd3197/CachiBot★ 19same name
- minh2004pd/chatbotfullpipeline★ 18same name
- emaraschio/cursor-commands★ 9same name
- soumatheusgomes/agentville★ 9same name
- peopleforrester/claude-dotfiles★ 3same name
- fotoflo/claude-skills★ 2same name
- lodetomasi/claude-code-training-lab★ 2same name
- Pradnyeshp/Claude-Skills★ 2same name
8 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 repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
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 8
Run formatting and lint checks using the project Makefile.
- Very specific: line 12
Run make format to format code.
- Very specific: line 13
Run make lint to check for violations.
- Distinctive: line 18
When lint or format issues are detected or when you need to ensure code quality:
- Very specific: line 20
Run make format then make lint.
“Common” is measured: kept by at least 6 in 10 of the 17 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
Lint Fix
Run formatting and lint checks using the project Makefile.
Workflow
- Run
make formatto format code. - Run
make lintto check for violations. - Address any remaining lint failures manually if needed.
Usage
When lint or format issues are detected or when you need to ensure code quality:
- Run
make formatthenmake lint.
Progressive Disclosure
- Makefile target definitions: Makefile at repo root.
Related Skills
- Plugin verification:
../plugin-verification/SKILL.md - Agent skills implementation:
../implement-agent-skills/SKILL.md
Sources
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.

