lint-fix
Skill2 starsChanged 4 months agoMITView on GitHub
Detect the project's linter and formatter, run them, and fix the reported problems — auto-fixable ones first, then the rest by hand — without changing behavior. Use when the user says "fix the lint errors", "run the linter", "format this code", "clean up lint warnings", "make lint pass", or "fix formatting".
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 commit, security-audit and 3 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.
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
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
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
- yu-iskw/meta-agent-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 repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
If no linter is configured, say so and suggest adding one (hand off to ci-setup) rather than inventing rules.
- Distinctive: line 36
Use the project's config as the source of truth.
- Very specific: line 37
Prefer fixing over suppressing.
- Distinctive: line 38
Keep auto-fix and manual changes reviewable: don't bundle unrelated edits.
“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
Linter & formatter config
!ls .eslintrc .eslintrc.js .eslintrc.json .eslintrc.cjs eslint.config.js eslint.config.mjs .prettierrc .prettierrc.json prettier.config.js biome.json ruff.toml .ruff.toml .flake8 setup.cfg pyproject.toml .rubocop.yml .golangci.yml .golangci.yaml rustfmt.toml .editorconfig 2>/dev/null
!cat package.json 2>/dev/null | grep -A30 '"scripts"' | grep -iE 'lint|format|fmt|prettier|biome|eslint' | head -20
Instructions
Find the project's linter/formatter, run it, and fix what it reports (scope to $ARGUMENTS if given). Use the project's own tooling and config — never impose your own style.
Method
- Identify the configured tools from the files and scripts above. Common stacks:
- JS/TS: ESLint and/or Prettier, or Biome. Prefer the project's npm scripts (
npm run lint,lint:fix,format) when they exist. - Python: Ruff, Flake8, Black, isort. Prefer
ruff check --fix/black/isortper config. - Go:
gofmt/goimports,golangci-lint run. - Rust:
cargo fmt,cargo clippy. - Ruby:
rubocop -a. If no linter is configured, say so and suggest adding one (hand off toci-setup) rather than inventing rules.
- JS/TS: ESLint and/or Prettier, or Biome. Prefer the project's npm scripts (
- Run the check first (read-only) to see the full set of problems and their counts. If a tool isn't installed, report that and how to install it instead of guessing.
- Apply safe auto-fixes using the tool's own fixer (
--fix,-a,--write,cargo fmt). Let formatters and rule-fixers do the mechanical work — don't hand-edit what a tool can fix deterministically. - Re-run, then fix the remainder by hand. For each manual fix, understand the rule before changing code, and make the minimal change that satisfies it while preserving behavior. Group by rule so the edits are consistent.
- Re-run until clean (or until only intentional, suppression-worthy cases remain). Show the before/after problem counts.
Rules
- Behavior-preserving only. Linting is cleanup, not refactoring or bug-fixing — if a lint rule is flagging a real bug, point it out separately rather than silently changing logic.
- Use the project's config as the source of truth. Don't add, remove, or relax rules, and don't reformat with different settings than the project uses. If a rule seems wrong, raise it with the user instead of editing the config.
- Prefer fixing over suppressing. Only add an inline disable (
// eslint-disable-next-line,# noqa) when the rule genuinely shouldn't apply, and add a brief reason — never blanket-disable to make output green. - Keep auto-fix and manual changes reviewable: don't bundle unrelated edits. If a formatter would reflow huge swaths of untouched code, flag that and confirm scope before committing to it.
- Summarize what ran, what was auto-fixed vs. hand-fixed, the remaining count, and anything you suppressed or that needs a human decision.
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.

