typo-checker

Detect and correct typos in codebases using typos-cli.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/tommy0103/vitest_lab --skill typo-checker-tommy0103
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typo-checker
Source: https://github.com/tommy0103/vitest_lab/tree/main/.claude/skills/typo-checker
Command: npx skills add https://github.com/tommy0103/vitest_lab --skill typo-checker-tommy0103

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and fixing typos in codebases, reducing manual review time and improving code quality.

Core Features & Use Cases

  • Typos Detection: Run typos-cli to find spelling errors across source files.
  • Review and Classify: Analyze findings to distinguish real typos from false positives.
  • Code and Documentation Fixes: Automatically correct typos in comments, variables, and documentation.
  • Maintain Custom Wordlists: Update _typos.toml to suppress known false positives and domain-specific abbreviations.
  • Use Case: Regularly run this skill during code reviews to catch and fix misspellings before deployment.

Quick Start

Run typos-cli on your project directory to identify spelling errors, then fix the confirmed typos and update configuration as needed.

Frequently Asked Questions about typo-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and fix typos in my codebase automatically?

You can detect and fix typos in your codebase by running typos-cli across your source files to identify spelling errors, then applying corrections to comments, variables, and documentation to improve code quality.

How do I handle false positives when running a spellcheck on source code?

You can handle false positives during a spellcheck by maintaining a custom wordlist in the _typos.toml configuration file, which suppresses known false positives and domain-specific abbreviations from future scans.

Do I need to install typos-cli to check for spelling errors in my project?

Yes, you need to install typos-cli to check for spelling errors, as this automation integrates directly with the tool to scan source files and manage configuration for false positive handling.

What is the best way to automate spelling error detection during code reviews?

The best way to automate spelling error detection during code reviews is to run typos-cli on your project directory to find errors, fix confirmed typos, and update configuration files to maintain documentation accuracy before deployment.

Can I correct misspellings in both code comments and documentation?

Yes, you can correct misspellings in both code comments and documentation, as the detection process scans across source files to identify and fix errors in variables, comments, and project documentation.

Why does typos-cli flag domain-specific abbreviations as spelling errors?

Typos-cli flags domain-specific abbreviations as spelling errors because it uses a standard dictionary, but you can resolve this by adding the terms to your _typos.toml file to prevent future false positives.