check-spelling
Skill887 starsChanged 30 days 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
- heaths/azsdk-samples-mcpedited, first seen Feb 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- heaths/azsdk-samples-mcp★ 024% 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- eng/tools/generate_api/AGENTS.mdAGENTS.md
- samples/AGENTS.mdAGENTS.md
- sdk/core/AGENTS.mdAGENTS.md
- sdk/cosmos/AGENTS.mdAGENTS.md
- sdk/cosmos/azure_data_cosmos_emulator/AGENTS.mdAGENTS.md
- sdk/cosmos/docs/AGENTS.mdAGENTS.md
- agentic-workflowsSkill
- analyze-codeSkill
- create-crateSkill
- create-hotfixSkill
- create-perf-testSkill
- create-recorded-testSkill
- document-cratesSkill
- export-apiSkill
- lint-markdownSkill
- prepare-releaseSkill
- review-doc-commentsSkill
- update-emitterSkill
- update-rustSkill
- cosmos-design-structSkill
- cosmos-pre-commit-validationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Run the same command again used to check spelling.
≈ “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.
Files
Spell checking
Usage
Get all staged and unstaged non-deleted files, then pipe them to the spell check script:
{ git diff --staged --name-only --diff-filter=d; git diff --name-only --diff-filter=d; } | sort -u | ./eng/common/spelling/Invoke-Cspell.ps1Configuration
The root configuration is .vscode/cspell.json, and CI runs cSpell with this config via eng/common/spelling/Invoke-Cspell.ps1.
Each service directory (e.g., sdk/{service-directory}) or crate directory (e.g., sdk/{service-directory}/{crate-directory}) can have a .cspell.json that should import either a parent .cspell.json or .vscode/cspell.json from the root of the repo. Per-directory configs are loaded based on the paths of files being checked.
Fix spelling
Show a summary of the misspellings to the user. Prompt the user for which words should be replaced and which should be ignored.
For words that should be replaced, fix the misspellings directly in the source files. If you cannot confidently determine the correct spelling, ask the user.
For words that should be ignored, add them to the ignoreWords array in a .cspell.json file under sdk/{service-directory} or lower. If the file doesn't exist, create it with an import of either a parent .cspell.json or ../../.vscode/cspell.json from the root of the repo.
Example sdk/keyvault/.cspell.json:
{
"import": [
"../../.vscode/cspell.json"
],
"ignoreWords": [
"ciphertext",
"purgeable"
]
}Seldom used words can be ignored within the file they are used by adding an appropriate comment e.g.:
// cspell:ignore {word}To disable cSpell for just the next line, use cspell:disable-next-line.
Testing
Run the same command again used to check spelling. All misspellings should be fixed.
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
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.

