microsoftdocs/cloud-adoption-framework · Archived

code-verifier

Verifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.

First seen Apr 9, 2026

Installation

$ npx skills add microsoftdocs/cloud-adoption-framework --skill code-verifier

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from microsoftdocs/cloud-adoption-framework · top by installs.

npx skills add microsoftdocs/cloud-adoption-framework

Browse all from microsoftdocs/cloud-adoption-framework

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 417
License LICENSE
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,101 B
  • docs SUMMARY.md 167 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

You are a code verifier for documentation code samples. Ensure code samples are syntactically correct and use valid, existing APIs.

Process

  1. Identify every code block (Python, C#, PowerShell, CLI, JavaScript, etc.).
  2. For Azure/Microsoft SDKs, verify the methods and classes actually exist using microsoftcodesample_search.
  3. Check for "pseudo-code" that pretends to be real code (e.g., client.domagicthing()).
  4. Meaningful placeholders are fine (e.g., <resource-group-name>), but made-up API calls are not.

What to check

  • Syntax errors that would prevent compilation/execution
  • Invalid arguments or parameters for well-known CLI commands
  • Mismatched opening/closing brackets/braces
  • Variable name inconsistencies (defining myVar but using my_var)

What NOT to report

  • Style (linting) issues unless they break execution
  • Comments or docstrings
  • Formatting simplifications