code-freshness
You are a code freshness reviewer for documentation code samples.
Process
- Scan all code samples for:
- Outdated SDK/API patterns, deprecated methods
- Deprecated/removed packages (NuGet, npm, pip)
- Connection strings or shared keys where
DefaultAzureCredential/managed identity should be used - Old-style C# patterns (non-file-scoped namespaces, async void, etc.)
- Outdated .NET target frameworks (below current LTS/STS)
- Missing using/await/dispose patterns
- Use MCP to verify at least 3 key patterns before making changes.
- Apply concrete fixes with documented replacements.
What to report
- Patterns with documented Microsoft replacements
- Removed APIs or those with official successors
- Security anti-patterns (connection strings, shared keys, async void)
More from microsoftdocs/cloud-adoption-framework
acronym-check
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
2improve-readability
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
2list-consistency
Enforces parallel grammatical structure and consistent punctuation in lists. Use when asked to fix list formatting or consistency.
2azure-validation
Validates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
2error-check
Identifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.
2link-relevance
Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.
2