lint-fix
Skill0 starsChanged 7 months agoMITView on GitHub
Run typecheck and lint, then fix all errors and warnings to zero. Use when asked to "do typecheck and lint", "fix lint errors", "fix all warnings", "clean up lint", or any request to make typecheck/lint pass clean. Applies a systematic batch-fix workflow rather than fixing issues one at a time.
18 other projects use a version of this.
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 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.
- autopilot-executeSkill
- close-planSkill
- deep-modules-auditSkill
- docs-auditSkill
- execute-phaseSkill
- living-design-systemSkill
- phased-planSkill
- responsive-auditSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
4
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 22
Before running anything, check package.json scripts and config files to determine:
- Distinctive: line 35
Run typecheck and lint in parallel to get the full picture upfront:
- Distinctive: line 46
Run the linter's auto-fix to eliminate mechanical issues (import order, duplicate imports, array type style, unused directives):
- Distinctive: line 76
Read all files for the current pattern category in a single parallel tool call.
- Distinctive: line 95
If anything remains, go back to Step 3 with the smaller set.
- Very specific: line 115
Always include a -- reason comment after eslint-disable-line so future readers (human or agent) understand the intent:
“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
A systematic workflow for driving typecheck and lint to zero errors, zero warnings.
Philosophy
- Zero tolerance — warnings are future errors. Fix them all, not just what's red.
- Auto-fix first — let the tooling do its job before you touch anything.
- Fix by pattern, not by file — categorize issues, then sweep each category across the whole codebase in one pass.
- Parallel everything — run typecheck and lint simultaneously; batch-read all affected files at once.
- Verify after every round — never assume fixes are clean. Re-run both checks after each batch of changes.
- Know when to suppress vs. fix — not every warning is a bug. Animated refs are stable. Platform checks are static. Add
eslint-disablewith an explanation, not blindly.
Step 0: Detect Project Tooling
Before running anything, check package.json scripts and config files to determine:
| What | How to detect |
| Typecheck command | package.json scripts: typecheck, type-check, tsc, or fall back to npx tsc --noEmit |
| Lint command | package.json scripts: lint. Check for ESLint config (.eslintrc*, eslint.config.*), Biome (biome.json), or framework wrappers (expo lint, next lint) |
| Auto-fix flag | ESLint: --fix. Biome: check --fix. Expo: expo lint -- --fix |
| Package manager | bun.lockb/bun.lock → bun, pnpm-lock.yaml → pnpm, yarn.lock → yarn, else npm |
Workflow
Step 1: Discover
Run typecheck and lint in parallel to get the full picture upfront:
# Adapt these to the project's actual commands
npx tsc --noEmit 2>&1 | head -100 &
npm run lint 2>&1 | head -100 &
waitStep 2: Auto-fix
Run the linter's auto-fix to eliminate mechanical issues (import order, duplicate imports, array type style, unused directives):
# ESLint
npx eslint . --fix
# Or framework wrapper
npx expo lint -- --fix
npx next lint --fix
# Or Biome
npx biome check --fix .This typically resolves 30-60% of warnings with zero risk.
Step 3: Categorize remaining issues
Group what's left by pattern, not by file:
| Pattern | Example | Fix strategy |
| Conditional hooks | useState / useMemo / useCallback called after an early return | Move all hooks above the first conditional return |
| Unescaped entities | ' or " in JSX text content | Replace with ' / " |
| Missing hook deps (real) | A function or value genuinely needed in the dep array | Add the dependency, or wrap the value in useCallback/useMemo |
| Missing hook deps (stable refs) | Animated values (useSharedValue), platform constants, router singletons | Add eslint-disable-line react-hooks/exhaustive-deps with a -- comment explaining why it's safe |
| Type errors | Wrong types, missing properties, etc. | Fix the types to match the actual runtime contract |
| Unused variables/imports | Imported but not used | Remove them (auto-fix usually catches these) |
| Any pattern | @typescript-eslint/*, no-explicit-any, etc. | Fix the underlying issue; suppress only with explanation |
Step 4: Batch-read affected files
Read all files for the current pattern category in a single parallel tool call. Don't fix one file, re-run, fix the next — that's O(n) round trips.
Step 5: Batch-fix by pattern
Apply the same class of fix across all affected files in one pass:
- Conditional hooks: For each file, move all
useState/useMemo/useCallback/custom hook calls above the firstif (...) return. The early return stays — it just moves below the hooks. - Unescaped entities: Find-and-replace literal
'→'and"→"in JSX text nodes only (not in props or JS expressions). - Platform-conditional hooks (e.g.
if (Platform.OS === 'web') return stub; return useNativeHook()): Restructure so the hook is always called, then conditionally return the result. Add eslint-disable if the branch is truly static.
Step 6: Verify
Re-run both typecheck and lint:
npx tsc --noEmit 2>&1
npm run lint 2>&1If anything remains, go back to Step 3 with the smaller set. Repeat until output is clean.
Step 7: Confirm zero
The final run must show:
- TypeCheck: no output (clean)
- Lint: no
✖ N problemsline, or explicitly0 problems
When to suppress vs. fix
Suppress (eslint-disable with explanation) when:
- The dependency is a Reanimated shared value — created by
useSharedValue, these are stable refs that never change identity - The effect intentionally runs only once on mount and the "missing" deps (like
router) are stable singletons - The code branches on
Platform.OS— this is a build-time constant, the branch is always the same
Fix (add the dep or restructure) when:
- The missing dep is a function defined in the component body — wrap it in
useCallback - The missing dep is derived state that genuinely changes — add it to the array
- The hook is called conditionally — restructure to call unconditionally
Always include a -- reason comment after eslint-disable-line so future readers (human or agent) understand the intent:
}, [visible]); // eslint-disable-line react-hooks/exhaustive-deps -- animated values are stable refsCommon anti-patterns to avoid
- ❌ Fixing one file at a time, re-running lint after each fix
- ❌ Adding
// @ts-ignoreor blanketeslint-disablewithout understanding the issue - ❌ Only fixing errors and leaving warnings "for later"
- ❌ Adding every suggested dependency to a
useEffectdep array without thinking (causes infinite loops with animated values) - ❌ Running typecheck and lint sequentially when they're independent
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.

