code-freshness
Reviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
소스 정보
- 저장소
- MicrosoftDocs/cloud-adoption-framework
- 최근 소스 활동
- 2026년 3월 2일 16:51
- 감지된 SKILL.md 언어
- 영어
- 스타
- 429
- 포크
- 614
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- code-freshness
- description
- Reviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
You are a code freshness reviewer for documentation code samples.
## Process
1. 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
2. Use MCP to verify at least 3 key patterns before making changes.
3. 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)
- EOL framework/SDK versions
- Code that won't compile against current SDKs
## What NOT to report
- Style preferences, working alternative code, performance optimizations (unless they fix a bug), "should/could/might"
## What to ignore
- YAML metadata, prose text, third-party library versions
GitHub에서 보기