agentsclimarketplace

Vp cspell

Skill VdustR/skills/skills/vp-cspell

Reusable Agent Skills by VdustR

Install
npx -y skills add VdustR/skills --skill vp-cspell

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Handle cspell unknown word warnings with a prioritized decision tree and config bootstrapping. Use when users encounter cspell diagnostics, spelling errors from cspell, CI or linting failures on unrecognized words, or ask to add words to the cspell dictionary, suppress cspell warnings, or choose between cspell:words and cspell:ignore directives. Also trigger when setting up cspell in a new project, when any cspell-related IDE warning appears, or when a pre-commit hook fails due to unknown words. Boundary: not for non-cspell spell checkers (typo, codespell, Vale, textlint) or other linting tools (ESLint, markdownlint).

SKILL.md

4.1 KB, as published. Nobody here has run it

cspell

Prioritized strategy for handling cspell unknown word warnings. Classify each flagged word, pick the narrowest fix, and optionally bootstrap cspell config for projects that don't have it yet.

Core Principles

  1. Config Check First — Verify repo has cspell config before any action; offer bootstrap if missing
  2. Adjust Text Before Adding to Dictionary — Restructure words (hyphenate, camelCase) when safe
  3. Narrowest Scope Wins — Inline directive for one-off words; project dictionary for recurring terms

Documentation: Fetch cspell syntax and config details via Context7 (/streetsidesoftware/cspell) at runtime; never rely on hardcoded syntax.

Workflow

  1. Check for cspell config — Search from the file's directory upward for cspell config files: package.json (cspell field), .cspell.json, cspell.json, cspell.config.{json,mjs,js,cjs,yaml,yml,toml}, cspell.{yaml,yml}, and their ./.config/ prefixed variants (e.g., .cspell.config.yaml, .config/cspell.json). Also check .vscode/cspell.json. If none found: notify user, do NOT auto-fix, offer to bootstrap (see below). Note: cspell.* settings in .vscode/settings.json are IDE-local and do not count as project config.
  2. Apply fix priority — Stop at the first applicable level (see table below).
  3. Select directive — When using inline directives, consult decision-tree.md for the selection guide.

Fix Priority

PriorityStrategyWhen to Use
1Adjust textCompound word cspell doesn't recognize; restructuring is safe (hyphenate, camelCase). See decision-tree.md for the full exception list
2Project dictionaryWord appears in 2+ files or is expected to recur project-wide
3Inline directiveOne-off word in a single file/location. See decision-tree.md for directive selection and placement

Config Bootstrapping

When a repo has no cspell config and the user wants to add one, guide through an interactive Q&A flow.

See config-bootstrapping.md for the full interactive setup flow.

Guidelines

  • Place cspell:words at file top for discoverability
  • Verify the flagged word is genuinely unknown — it may just need an existing dictionary enabled, and some flagged words are correct as written
  • Never replace words with semantically different alternatives
  • Never hyphenate or restructure runtime API identifiers, package names, or fixed external terms
  • Don't use cspell:disable to suppress large sections when individual words can be handled

Error Handling

ErrorAction
No write permission to configNotify user, suggest manual edit path
Excessive cspell . outputScope to source directory, configure ignorePaths first
Context7 unavailableFall back to cspell.org or cspell init --help

For bootstrapping-specific errors (cspell CLI not installed, cspell init fails), see config-bootstrapping.md.

Reference Files

  • decision-tree.md — Full decision flowchart, text adjustment rules and exceptions, dictionary vs inline criteria, directive selection, edge cases
  • config-bootstrapping.md — Interactive setup flow, stack detection, CI integration, post-init adjustments

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.