Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

FrankDannie
Copy link

@FrankDannie FrankDannie commented Sep 1, 2025

What does this PR do?

This PR sets up cspell for the MCP repository to help detect spelling issues across tools.

GitHub issue number?

#89

Changes included:

  1. Added .cspell-common.yaml containing repo-wide common words.
  2. Added generate-cspell.sh script to regenerate tool-specific word lists.

With this setup:

  • Unknown words per tool are tracked in their cspell.yaml.
  • Common words are centralized in .cspell-common.yaml.
  • The repository is ready for consistent spell checking across all tools.

All tools have been scanned, and no unknown words were found at this point.

Pre-merge Checklist

  • Required for All PRs
    • Read contribution guidelines
    • PR title clearly describes the change
    • Commit history is clean with descriptive messages (cleanup guide)
    • Added comprehensive tests for new/modified functionality
    • Updated CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
    • Spelling check passes: .\eng\common\spelling\Invoke-Cspell.ps1
  • For MCP tool changes:
    • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
    • Updated README.md documentation
    • Updated command list in /docs/azmcp-commands.md
    • Updated test prompts in /docs/e2eTestPrompts.md
    • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • 👉 For Community (non-Azure team member) PRs:
    • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
    • Manual tests run: added comment /azp run azure - mcp to run Live Test Pipeline

- Added .cspell-common.yaml with repo-wide words
- Generated per-tool cspell.yaml files importing common words
@FrankDannie
Copy link
Author

@microsoft-github-policy-service agree

@FrankDannie please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

feiskyer pushed a commit to feiskyer/microsoft-mcp that referenced this pull request Sep 8, 2025
* Remove explicit eng-sys ownership
* Revert script changes
@jongio
Copy link
Contributor

jongio commented Oct 6, 2025

@hallipr - Do we need this given we already have cspell?

@hallipr
Copy link
Member

hallipr commented Oct 13, 2025

@jongio, we do have cspell, but could use custom config support per tool or server if needed. See #89

@hallipr
Copy link
Member

hallipr commented Oct 13, 2025

Hi @FrankDannie, thanks for the PR. We already have cspell in the repo (see .vscode/cspell.json) and our pipelines run a script that installs cspell and looks for that common config (eng/common/spelling/Invoke-Cspell.ps1)

But we could use a more standardized way of defining new words per server or tool and have issue #89 open for that work. Ideally, each tool or server folder could have its own config and could reference the main config at .vscode/cspell.json. We'd just need to be sure our Invoke-Cspell.ps1 still honors the per-directory configs as well.

@g2vinay g2vinay added the Do Not Merge Do Not Merge / WIP PRs label Oct 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Merge Do Not Merge / WIP PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.