lint-fix
Skill1 starsChanged 9 months agoMITView on GitHub
Auto-format code and fix linting issues across Python and JavaScript/TypeScript projects. Use when cleaning up code, fixing style issues, or preparing for commit.
Files
Universal Linter & Formatter
Auto-detect project type and run appropriate formatters and linters with auto-fix.
Arguments
$ARGUMENTS: Specific path or file to lint (optional - uses current directory)
Detection & Tools
Python Projects
Formatters:
black- Code formatterisort- Import sorter
Linters:
flake8- Style checkermypy- Type checkerruff- Fast linter (replaces flake8, isort)
Execution Order:
# 1. Sort imports
uv run isort $PATH --profile black
# or with ruff
uv run ruff check --select I --fix $PATH
# 2. Format code
uv run black $PATH
# 3. Lint (auto-fix what's possible)
uv run ruff check --fix $PATH
# or
uv run flake8 $PATH
# 4. Type check (no auto-fix)
uv run mypy $PATHJavaScript/TypeScript Projects
Formatters:
prettier- Code formatter
Linters:
eslint- Linter with auto-fix
Execution Order:
# 1. Format with Prettier
npx prettier --write $PATH
# or with pnpm
pnpm prettier --write $PATH
# 2. Lint with ESLint (auto-fix)
npx eslint --fix $PATH
# or
pnpm eslint --fix $PATH
# 3. Type check (TypeScript only)
npx tsc --noEmitProject-Specific Configurations
| Project | Tools | Config Files |
| eruditiontx-services-mvp | black, flake8, cleanpy | pyproject.toml, .flake8 |
| mathmatterstx-services | black, flake8 | pyproject.toml |
| eruditiontx-client-mvp | ESLint, Prettier | .eslintrc, .prettierrc |
| erudition-math-v2 | ESLint, Prettier | eslint.config.mjs |
| notaryo.ph | ESLint, Prettier | eslint.config.mjs, prettier.config.js |
| bocs-turbo | ESLint, Prettier | Workspace configs |
Pre-commit Integration
Many projects use pre-commit hooks. Run manually:
# Python projects
pre-commit run --all-files
# This runs all configured hooks:
# - black
# - flake8
# - isort
# - cleanpy (remove __pycache__)Staged Files Only
For commit preparation, lint only staged files:
# Python
git diff --cached --name-only --diff-filter=ACMR | grep '\.py$' | xargs black
git diff --cached --name-only --diff-filter=ACMR | grep '\.py$' | xargs flake8
# JavaScript/TypeScript
git diff --cached --name-only --diff-filter=ACMR | grep -E '\.(js|jsx|ts|tsx)$' | xargs npx prettier --write
git diff --cached --name-only --diff-filter=ACMR | grep -E '\.(js|jsx|ts|tsx)$' | xargs npx eslint --fixOutput Format
Lint & Format: [project-name]
Path: [path or .]
Project Type: [Python/JavaScript/TypeScript]
1. Formatting...
[Formatter output]
Files formatted: X
2. Linting...
[Linter output]
Issues fixed: Y
Issues remaining: Z
3. Type Checking...
[Type checker output]
Type errors: N
Summary:
Formatted: X files
Auto-fixed: Y issues
Manual fixes needed: Z issues
Type errors: NCommon Issues & Fixes
Python
- Line too long: Black handles this, or add
# noqa: E501 - Import order:
isortorruff check --select I --fix - Unused imports:
ruff check --select F401 --fix
JavaScript/TypeScript
- Unused variables: ESLint
--fixwithno-unused-vars - Missing semicolons: Prettier handles this
- Inconsistent quotes: Prettier handles this
Skip Linting
For files that should be skipped:
# Python: Add to file
# flake8: noqa
# type: ignore// JavaScript: Add to file
/* eslint-disable */
// prettier-ignoreOther versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- getsentry/sentry★ 46ksame 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
- 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.
Used alongsideProjects with it also use docstring, changelog 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.
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 4 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
In this repository125 other files it gives its agents.
- skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- address-sanitizerSkill
- aflppSkill
- algorand-vulnerability-scannerSkill
- algorithmic-artSkill
- ask-questions-if-underspecifiedSkill
- atherisSkill
- audit-context-buildingSkill
- audit-prep-assistantSkill
- autonomous-skillSkill
- aws-skillsSkill
- better-authSkill
- brainstormingSkill
- brand-guidelinesSkill
- burpsuite-project-parserSkill
- cairo-vulnerability-scannerSkill
- canvas-designSkill
- cargo-fuzzSkill
- changelog-generatorSkill
- claude-in-chrome-troubleshootingSkill
- cloudflare-skillsSkill
- code-maturity-assessorSkill
- codeqlSkill
- codex-skillSkill
- constant-time-analysisSkill
- constant-time-testingSkill
- cosmos-vulnerability-scannerSkill
- coverage-analysisSkill
- d3js-visualizationSkill
- db-resetSkill
- deep-researchSkill
- deploySkill
- dev-startSkill
- differential-reviewSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- doc-generateSkill
- documentationSkill
- docxSkill
- dwarf-expertSkill
- entry-point-analyzerSkill
- env-checkSkill
- executing-plansSkill
- expo-skillsSkill
- finishing-a-development-branchSkill
- firebase-apk-scannerSkill
- fix-reviewSkill
- frontend-designSkill
- fuzzing-dictionarySkill
- fuzzing-obstaclesSkill
- git-automationSkill
- google-design-mdSkill
- guidelines-advisorSkill
- harness-writingSkill
- health-checkSkill
- huggingface-skillsSkill
- insecure-defaultsSkill
- internal-commsSkill
- The first 60 shown.
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.

