Check and fix spelling in project source files using cSpell.
npx skills add https://github.com/Azure/azure-sdk-for-rust --skill check-spelling
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.ps1
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.
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.
Run the same command again used to check spelling. All misspellings should be fixed.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take azure/check-spelling from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.