How this skill is triggered — by the user, by Claude, or both
Slash command
/linting:check-spellingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search for a `package.json` in the current working directory and each ancestor directory up to and including the repository root.
Search for a package.json in the current working directory and each ancestor directory up to and including the repository root.
If an ancestor package.json has cspell in devDependencies, run npm install from that package.json directory to install it, then run npx cspell <command> from the current working directory.
If no ancestor package.json contains cspell in devDependencies, run npx -y cspell <command> from the current working directory instead. Do not add cspell to any package.json or install it permanently.
cSpell configuration including custom dictionaries and word lists can be found in files:
cspell.jsoncspell.config.jsoncspell.yaml or cspell.ymlcspell.config.yaml or cspell.config.ymlThey may be prefaced with an optional . or in a .config/ directory e.g.:
.cspell.json.config/cspell.yaml.config/.cspell.ymlThey may also be located in a .vscode/ directory e.g.:
.vscode/cspell.jsonIf a suitable configuration is not found, create a .cspell.json file in the root of the repository.
The configuration file schema is described at https://raw.githubusercontent.com/streetsidesoftware/cspell/v<version>/cspell.schema.json where <version> should match the cspell version from the ancestor package.json devDependencies (e.g., v9.6.2). If no ancestor package.json contains cspell in devDependencies, use https://raw.githubusercontent.com/streetsidesoftware/cspell/main/cspell.schema.json.
Always include the schema URI in the $schema field and set the current project language e.g., "en".
Inside a git repository you should also set useGitignore to true in the configuration file.
When running any cspell command, pass --config <path> with the path to the configuration file.
Run npx cspell lint [options] [globs...] to check a list of file globs or . for the directory tree.
Show a summary of the misspelling to the user. Prompt the user for which words should be replaced with another word. All remaining words should be added to the dictionary using the steps below.
A project may have multiple cspell configuration files at different directory levels. When adding a word to the words array, select the configuration file as follows:
This prevents the same word from being duplicated across multiple configuration files.
If any misspellings are only in files that match any filename globs in an optional overrides section of the chosen configuration file, add those words to the words array in that override according to the schema.
Seldom used words can be ignored within the file they are used by adding an appropriate comment e.g.:
// cspell:ignore <word>
Run the same command again used to check spelling. All misspellings should be fixed.
npx claudepluginhub heaths/plugins --plugin lintingChecks Spanish spelling (accents/tildes, agreement, typos) in code comments, documentation, UI strings, and git commits. Useful for Spanish-language projects.
Formats and validates code files with Prettier for JS, TS, JSON, CSS, MD. Checks compliance, creates .prettierrc/.prettierignore, sets up pre-commit hooks.
Bootstraps or updates projects for Claude Code — generates CLAUDE.md with progressive disclosure docs, installs auto-format hooks, sets up test infrastructure, audits existing docs against source code. Supports single projects, monorepos, and multi-repo workspaces.