typo-checker

Identify and fix typos in codebases using typos-cli and update _typos.toml.

16.9k|1.9k|Updated Dec 3, 2021
One-click install
npx skills add https://github.com/vitest-dev/vitest --skill typo-checker-vitest-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typo-checker
Source: https://github.com/vitest-dev/vitest/tree/main/.claude/skills/typo-checker
Command: npx skills add https://github.com/vitest-dev/vitest --skill typo-checker-vitest-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaboratively maintain code quality by automatically identifying typos in the codebase, documentation, and comments using typos-cli, reviewing findings, fixing real typos, and updating the _typos.toml configuration to suppress false positives.

Core Features & Use Cases

  • Scan the repository with typos-cli to surface typos across source, docs, and test files.
  • Classify findings into real typos vs false positives and update _typos.toml to suppress recurring issues.
  • Apply fixes across files and commit changes to keep the codebase clean and consistent.

Quick Start

Run typos-cli on your codebase to identify typos, review findings, fix real typos, and update _typos.toml to suppress false positives.

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 find and fix typos by running typos-cli to scan source files, documentation, and tests, then applying fixes to real typos and committing the changes to maintain codebase hygiene.

What is the best way to handle false positives from typos-cli during codebase linting?

The best way to handle false positives during linting is to update the _typos.toml configuration file, adding suppression rules to prevent recurring issues from being flagged in future maintenance cycles.

Do I need to install typos-cli before scanning my repository for typos?

Yes, you need typos-cli installed and access to the repository before you can scan for typos, classify findings, and update the _typos.toml configuration to suppress false positives.

Can I use this typo checking workflow for pre-release checks across different languages?

Yes, this typo checking workflow applies to routine codebase hygiene, ongoing maintenance cycles, and pre-release checks across multiple languages and repositories, updating _typos.toml as part of the process.

How does updating _typos.toml improve codebase quality over time?

Updating _typos.toml improves codebase quality by suppressing recurring false positives, ensuring that subsequent typos-cli scans surface only real typos in source, docs, and test files.