fix-spelling

Resolve cspell unknown-word errors by rewording text or updating dictionaries, patterns, and suppressions.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Blotch-Smart-Frames/Board --skill fix-spelling-blotch-smart-frames
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-spelling
Source: https://github.com/Blotch-Smart-Frames/Board/tree/main/.claude/skills/fix-spelling
Command: npx skills add https://github.com/Blotch-Smart-Frames/Board --skill fix-spelling-blotch-smart-frames

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? cspell lint runs flag unknown words across a codebase, and fixing them ad hoc leads to bloated dictionaries, scattered suppressions, and inconsistent spelling. This Skill applies a strict decision tree that resolves each flagged word with the least-invasive correct fix, preferring rewording over config changes. ## Core Features & Use Cases - Reword-first resolution: Prioritizes rephrasing prose in American English (e.g., colour → color, datastore → data store) before touching any cspell configuration. - Scoped config management: Adds words, dictionaries, or regex patterns at the narrowest correct scope — inline comment, package-level cspell.json, or monorepo root. - Structured reporting: Outputs a per-word decision trace showing why rewording, dictionaries, or patterns were accepted or ruled out, then applies the fix. - Use Case: After running npx cspell on a monorepo and getting 30 unknown-word errors, use this Skill to triage each one — rewording prose, adding real technical terms to the right cspell.json, and suppressing one-off generated identifiers. ## Quick Start Run cspell on the repo and fix every unknown-word error it reports, preferring rewording over config changes.

Frequently Asked Questions about fix-spelling

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

FAQPage Schema
How do I fix cspell unknown word errors?▼

First try rewording the sentence so the flagged word disappears using words cspell already accepts. If the word must stay, add a covering dictionary, add the word to the narrowest cspell.json scope, match it with a regex pattern, or use an inline cspell comment as a last resort.

How to add words to cspell config in a monorepo?▼

Add the word at the narrowest correct scope: an inline cspell:words comment for one file, the package-level cspell.json for one package, or the root cspell.json for words used across packages. Keep the words array alphabetically sorted.

Should I reword text or add a word to the cspell dictionary?▼

Reword first whenever the flagged word is prose that can be naturally rephrased, including British spellings replaced with American forms. Only add words when the token is an identifier, proper noun, package name, or precise technical term with no natural substitute.

When should I use cspell regex patterns instead of words?▼

Use a patterns entry when the flagged token is a structured string appearing in many places, such as framework-generated identifiers, API tokens, date format strings, or vendor event names. Define the pattern and reference it in ignoreRegExpList.

Does cspell support British English spellings?▼

This workflow resolves everything toward American English, replacing forms like colour and cancelled with color and canceled. British spellings should never be added to dictionaries or words arrays; they are fixed by rewording to the US form.