typos

Scan code, comments, and docs for English and Korean typos and naming inconsistencies.

9|Updated Dec 21, 2016
One-click install
npx skills add https://github.com/ysoftman/myenv --skill typos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typos
Source: https://github.com/ysoftman/myenv/tree/main/.claude/skills/typos
Command: npx skills add https://github.com/ysoftman/myenv --skill typos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool scans code, comments, docs, and strings for spelling and naming inconsistencies in English and Korean across the entire project, helping maintain professional quality and reduce confusion.

Core Features & Use Cases

  • Cross-language typo detection: finds typos and inconsistent naming in code, comments, and docs in English and Korean.
  • Pre-commit readiness: runs before commits to catch issues early.
  • Use Case: when preparing a pull request, run the checker to identify and fix typos before merging.

Quick Start

Run typos to scan the repository and identify misspellings across code, comments, and docs.

Frequently Asked Questions about typos

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

FAQPage Schema
How do I scan my repository for spelling mistakes in code and comments?

To scan for spelling mistakes, run a typo checker across your repository to identify misspellings in source files, comments, and documentation, producing a structured report with file paths and suggested corrections.

Can I detect typos in both English and Korean source files?

Yes, typo detection supports both English and Korean text, scanning code, comments, and documentation to find spelling and naming inconsistencies across multilingual project files.

How do I check only changed files for typos before a git commit?

You can check changed files for typos before a commit by integrating the scanner as a pre-commit hook, using changed-file prioritization to catch issues early in review workflows.

What is the best way to fix naming inconsistencies across a project before a pull request?

The best way to fix naming inconsistencies before a pull request is running a full-repo scan that identifies typos and generates a structured report with original text and suggested corrections.

Does typo detection work on documentation files as well as source code?

Yes, typo detection scans documentation files alongside source code and comments, identifying spelling mistakes and naming inconsistencies across all project text for comprehensive review.