| name | azure-sdk-sample-review |
| description | Reviews Azure SDK samples for best practices, credentials, errors, and docs. Auto-detects language. |
| domain | sdk-review |
USE FOR
- "review Azure SDK sample"
- "check TypeScript/Python/.NET/Go/Java/Rust sample"
- Reviewing credential handling, error patterns, documentation in Azure SDK samples
- Reviewing quickstart articles for SDK guidance
- "SDK code review", "review sample credentials"
DO NOT USE FOR
- General code review unrelated to Azure SDK
- Production application code
- Azure service configuration
Context
Reviews Azure SDK code samples for publication. Supports TypeScript (@azure/*), Python (azure-*), .NET (Azure.*), Go (azcore), Java (com.azure.*), Rust (azure_*), and quickstart articles.
Language Detection
TS: .ts, @azure/* | Py: .py, azure-* | .NET: .cs, Azure.* | Go: .go, azcore | Java: .java, com.azure.* | Rust: .rs, azure_* | Quickstart: .md
Review Architecture — 3-Layer Model
Execute review in layer order. Earlier layers produce structured, high-confidence findings; later layers add nuance.
Layer 1: Pattern-Based Rules (ALWAYS run first)
Load rules/shared.yaml + rules/{language}.yaml. Apply pattern-matching rules to produce findings. These rules provide structured guidance for the reviewer — patterns to look for, anti-patterns to flag, and exceptions to consider.
Note: Rules are applied by a reviewer (human or LLM), not executed as a regex engine. Regex patterns serve as detection hints, not literal execution targets.
Output: List of rule violations with {rule_id, severity, location, fix}
Layer 2: Version & Deprecation Checks
Check imports/dependencies against:
versions/deprecated-packages.yaml — retired packages with replacements
versions/track1-packages.yaml — legacy SDK packages (auto-reject)
- External source of truth for current versions:
MicrosoftDocs/azure-dev-docs-pr/articles/includes/{language}-all.md
Output: Deprecated/Track 1 findings with migration guidance
Layer 3: LLM Judgment (informed by references)
Load references/shared/ + references/{language}/. Apply nuanced review for:
- Architecture and code structure quality
- Documentation completeness
- Naming and readability
- Patterns that rules can't catch (e.g., "is this the right service for this use case?")
Output: Advisory findings with recommendations
Review Approach
- Detect language from file extensions/imports
- Layer 1: Apply
rules/shared.yaml + rules/{language}.yaml deterministically
- Layer 2: Check
versions/deprecated-packages.yaml and versions/track1-packages.yaml
- Layer 3: Load
references/shared/ + references/{language}/ for judgment-based review
- Present findings grouped by severity: blocker > high > medium > low
Output Format
## Review: {filename}
### 🚫 Blockers (must fix)
| Rule | Location | Issue | Fix |
|------|----------|-------|-----|
| CRED-001 | line 5 | Hardcoded connection string | Use DefaultAzureCredential |
### âš ï¸ High (should fix)
...
### 💡 Medium/Low (consider)
...
### ✅ Strengths
...
References
References location: Supporting documents live inside this skill's directory at .github/skills/azure-sdk-sample-review/. Paths like references/file.md are relative to this skill folder, not the repo root.
Example
User: "Review this TypeScript sample"
Skill: Detects TypeScript → applies rules/shared.yaml + rules/typescript.yaml → checks versions/deprecated-packages.yaml → loads references/shared/ + references/typescript/ → reports findings by severity.