agentleFS
Sign inStart free
heathsheaths/azsdk-samples-mcp/.github/skills/check-spelling/SKILL.md

check-spelling

Skill0 starsChanged 9 months agoMITView on GitHub

Check and fix spelling in project source files using cSpell

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. Azure/azure-sdk-for-rust★ 88719% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run npm install from the repository root to install cspell from devDependencies in the root package.json.

    line 10
  2. Very specific:

    Run npx cspell lint --config .cspell.json .

    line 24
  3. Very specific:

    Add remaining words to .cspell.json:

    line 30
  4. Very specific:

    If a word appears only in files matching an existing override filename glob, add it to that override's words array.

    line 32
  5. Distinctive:

    Run the same command again used to check spelling.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spell checking

Installation and usage

Run npm install from the repository root to install cspell from devDependencies in the root package.json. Then run npx cspell <command> to use the locally installed version.

Configuration

The cSpell configuration is in .cspell.json at the repository root. When running any cspell command, pass --config .cspell.json.

The configuration has the following structure:

  • words: array of accepted words applied repo-wide.
  • overrides: array of per-glob overrides, each with a filename glob and its own words array. For example, **/tsconfig.json has its own word list.
  • ignorePaths: array of paths excluded from spell checking.

Check spelling

Run npx cspell lint --config .cspell.json . to check spelling across the repository.

Fix spelling

Show a summary of the misspelling to the user. Prompt the user for which words should be replaced with another word.

Add remaining words to .cspell.json:

  • If a word appears only in files matching an existing override filename glob, add it to that override's words array.
  • Otherwise, add it to the top-level words array.

Seldom used words can be ignored within the file they are used by adding an appropriate comment e.g.:

// cspell:ignore <word>

Testing

Run the same command again used to check spelling. All misspellings should be fixed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free