Typo Checker
- 18 installs
- 16.9k repo stars
- Updated August 4, 2026
- antfu/vitest
typo-checker is a Claude Code skill that runs typos-cli on a codebase, fixes real typos, and updates _typos.toml to suppress false positives.
About
This skill scans a codebase with typos-cli, classifies each finding as a real typo or a false positive, fixes the real ones, and maintains _typos.toml so false positives do not recur. A developer uses it for routine codebase hygiene or when spelling checks are mentioned. It covers scanning, classification patterns, fixing across comments, names, and filenames, and committing fixes with config updates.
- Runs typos-cli, classifies findings, and fixes real typos
- Maintains _typos.toml to suppress recurring false positives
- Uses typos --format=brief and respects .gitignore
Typo Checker by the numbers
- 18 all-time installs (skills.sh)
- Ranked #748 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
typo-checker capabilities & compatibility
- Capabilities
- spell check · code hygiene · lint fix
- Use cases
- code review · refactoring
What typo-checker says it does
Scan the codebase with `typos-cli`, classify findings, fix real typos, and maintain `_typos.toml` so false positives don't recur.
When in doubt about whether a misspelled variable name is "intentional" — it's still a typo.
npx skills add https://github.com/antfu/vitest --skill typo-checkerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 18 |
|---|---|
| repo stars | ★ 16.9k |
| Last updated | August 4, 2026 |
| Repository | antfu/vitest ↗ |
What it does
Scan a codebase with typos-cli, fix real typos, and maintain _typos.toml for false positives.
Who is it for?
Routine codebase typo maintenance and suppressing recurring false positives
Skip if: Grammar or prose style review beyond spelling
When should I use this skill?
Doing periodic codebase hygiene or when the user mentions typos or spelling checks
What you get
Real typos fixed and _typos.toml updated so false positives stop recurring
- Fixed typos
- Updated _typos.toml
By the numbers
- Five-step workflow: scan, classify, fix, update config, commit
Files
Typo Checker
Scan the codebase with typos-cli, classify findings, fix real typos, and maintain _typos.toml so false positives don't recur.
Prerequisites
typos-cli must be installed. If not available, install via one of:
| Method | Command |
|---|---|
| cargo | cargo install typos-cli |
| brew | brew install typos-cli |
| pipx | pipx install typos |
| Binary | Download from https://github.com/crate-ci/typos/releases |
Workflow
1. Scan
typos --format=briefThis outputs one finding per line: file:line:col: \typo\ -> \suggestion\``. Compact and easy to parse.
typos respects .gitignore by default, so node_modules/, dist/, build outputs are already excluded.
To get an overview first:
# Count unique typo words by frequency
typos --format=brief 2>&1 | sed "s/.*\`//;s/\`.*//" | sort | uniq -c | sort -rn | head -20If many findings come from minified/generated files, add those paths to _typos.toml extend-exclude first, then re-scan.
2. Classify each finding
For every finding, decide:
- Real typo — fix it
- False positive — add to
_typos.toml
Common false positive patterns:
- Short variable names that happen to be words (
ba,fo,nd) - Domain abbreviations (
alsfor AsyncLocalStorage,PnPfor Plug'n'Play) - File extensions in regexes (
.styl,.pcss) - Test fixture strings and test data
- Line truncation artifacts in inline snapshots (
afte...,wrapp...) - Product names and proper nouns
- Lorem ipsum text
When in doubt about whether a misspelled variable name is "intentional" — it's still a typo. Propagated typos are still typos. Fix them.
3. Fix real typos
- Comments, docs, JSDoc: fix the text directly
- Variable/property names: rename all occurrences consistently
- Test names: fix the name, update corresponding snapshot files
- Filenames: rename the file and update all imports/references — check for references before renaming
4. Update _typos.toml
Add false positives to [default.extend-words] with a comment explaining why:
[default.extend-words]
# AsyncLocalStorage abbreviation
als = "als"For file-level exclusions, use [files].extend-exclude:
[files]
extend-exclude = [
"*.js.map",
"*.svg",
]If _typos.toml doesn't exist yet, create it.
5. Commit
Commit fixes and config updates together:
chore: fix typos and update _typos.tomlRelated skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
How do I get a quick overview of typo findings?
Run typos --format=brief and pipe through sort and uniq to count unique typo words by frequency.
Is a misspelled variable name still a typo?
Yes; when in doubt it is still a typo, and propagated typos should be fixed across all occurrences.