lint
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user needs to run linting on the Go codebase and automatically fix any issues found. The skill should: - Check for required tools before running - Execute make lint command - Parse lint output to identify issues - Apply fixes using appropriate methods (edit, lsp_replace_symbol, etc) - Re-run linting to verify fixes - Handle different types of lint issues appropriately
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
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
- aiagentkit-labs/agentic-dev-kittheir own version, first seen Nov 8, 2026
- levi-qiao/obsidian-llm-wikitheir 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 17 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 26 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
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 4 projects that use this
AnthropicSkilldigest
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
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.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 68 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use when the user needs to run linting on the Go codebase and automatically fix any issues found.
- Distinctive: line 7
Verify required tools are available (go, gopls, staticcheck)
- Very specific: line 8
Run make lint to identify issues
- Distinctive: line 10
Verify fixes resolved all issues
- Distinctive: line 15
Check for required tools before running
- Distinctive: line 24
Must verify go, gopls, and staticcheck are available before running
- Very specific: line 25
Must run make lint as the primary lint command
- Distinctive: line 26
Must attempt to fix all reported issues
- Distinctive: line 27
Must verify fixes by re-running lint
- Distinctive: line 28
Should preserve code functionality while improving style
“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
lint
Use when the user needs to run linting on the Go codebase and automatically fix any issues found.
Usage
- Verify required tools are available (go, gopls, staticcheck)
- Run
make lintto identify issues - Analyze lint output and apply fixes
- Verify fixes resolved all issues
Implementation
The skill should:
- Check for required tools before running
- Execute
make lintcommand - Parse lint output to identify issues
- Apply fixes using appropriate methods (edit, lsp_replace_symbol, etc)
- Re-run linting to verify fixes
- Handle different types of lint issues appropriately
Requirements
- Must verify go, gopls, and staticcheck are available before running
- Must run
make lintas the primary lint command - Must attempt to fix all reported issues
- Must verify fixes by re-running lint
- Should preserve code functionality while improving style
Dependencies
- Go compiler (go)
- Go language server (gopls)
- Staticcheck tool
- Make build system
- Access to project files
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.

