lint-fix
Skill9 starsChanged 3 months agoMITView on GitHub
Fix lint issues in the current file
17 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- 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
- soumatheusgomes/agentvilletheir own version, first seen Aug 13, 2026
Used with
Projects with it also use docstring, changelog and 1 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
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- gologo13/agent-skills★ 085% same
Wrote their own version · 16
- getsentry/sentry★ 46ksame name
- dirien/yet-another-agent-harness★ 19same name
- jhd3197/CachiBot★ 19same name
- minh2004pd/chatbotfullpipeline★ 18same 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
- yu-iskw/meta-agent-skills★ 2same name
6 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 repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- create-pr-mainSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- setup-new-featureSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-memory-bankSkill
- update-readmeSkill
- write-unit-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
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
- could be automatic: a setting could enforce it
- Distinctive: line 20
Remove unused imports and variables
- Distinctive: line 21
Add missing semicolons or correct indentation
- Distinctive: line 43
Use the project linter config rather than personal or ad hoc rules.
- Distinctive: line 45
Do not commit, push, merge, or run production scripts without consent.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Overview
Analyze the current file for linting issues and automatically fix them according to the project's coding standards, then apply the fixes directly to the code and explain what changes were made.
Steps
- Identify linting issues
- Code formatting and style consistency
- Unused imports and variables
- Missing semicolons or proper indentation
- Best practice violations
- Type safety issues
- Apply fixes
- Fix formatting and style issues
- Remove unused imports and variables
- Add missing semicolons or correct indentation
- Apply best practice corrections
- Fix type safety issues
- Explain what changes were made
Lint and Fix Code Checklist
- Identified all code formatting and style issues
- Identified unused imports and variables
- Identified missing semicolons or indentation issues
- Identified best practice violations
- Identified type safety issues
- Applied all formatting and style fixes
- Removed unused imports and variables
- Fixed indentation and added missing semicolons
- Applied best practice corrections
- Fixed type safety issues
- Explained what changes were made
Guardrails
- Limit edits to formatting and style; do not change behavior while fixing lint.
- Use the project linter config rather than personal or ad hoc rules.
- Scope is the current file; if asked to fix lint across the whole repo, point to the repo-wide lint workflow (
/lint-suite) instead of silently linting one file. - Do not commit, push, merge, or run production scripts without consent.
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.