azsdk-common-sdk-release
Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 6.1k
- Forks
- 5.2k
01 前言 Front Matter
- name
- azsdk-common-sdk-release
- license
- MIT
- metadata
- { "version": "1.0.0", "distribution": "shared" }
- description
- Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.
- compatibility
- azure-sdk-mcp server, SDK package merged on release branch. Supports .NET, Java, JavaScript, Python, Go
02 资源文件 2
- 参考文档evals/eval.yaml2.1 KB
- 参考文档evals/trigger.eval.yaml3.3 KB
03 SKILL.md 正文
SDK Release
This skill checks release readiness and triggers the Azure SDK release pipeline for packages that are already prepared, guiding the user through prerequisite validation, readiness review, and the final pipeline launch with required approval steps.
Triggers
USE FOR: release SDK, trigger release, check release readiness, release pipeline, publish package, ship SDK WHEN: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK" DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation
Rules
- Requires the
azure-sdk-mcpserver; there is no CLI fallback for the release workflow. - Collect
packageNameandlanguage, then run the readiness check before attempting to trigger release. - If release is triggered, show the pipeline link and remind the user that the release stage still requires approval.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_release_sdk |
Check release readiness and/or trigger the release pipeline |
Steps
- Collect Info — Get
packageNameandlanguagefrom the user. Optionally getbranch(defaults to main). - Determine Intent — If the user explicitly asks to "check readiness" or "check if ready", run
azure-sdk-mcp:azsdk_release_sdkwithcheckReady: true. Otherwise, proceed to trigger the release directly. - Trigger Release — Run
azure-sdk-mcp:azsdk_release_sdkwithcheckReady: false(the default). Show pipeline link and inform user they must approve the release stage. - Review Results — If the release fails due to readiness issues, display failing checks and guide user to resolve.
Examples
- "Check if azure-storage-blob is ready for release"
- "Trigger release for @azure/core-rest-pipeline on JavaScript"
Troubleshooting
- If readiness check fails, review each failing prerequisite individually before re-triggering.
- Requires
azure-sdk-mcpserver. No CLI fallback — prompt user to configure MCP if unavailable.
04 同仓库更多 Skills
update-chat-api
Use when: updating, exporting, refreshing, or validating the public API baseline for Azure.Messaging.WebPubSub.Chat after a public API change.
search-documents
E2E workflow skill for Azure.Search.Documents SDK (TypeSpec + heavy customization). Handles full release cycles and partial updates: SHA update; code generation; build; customization fixes; ServiceVersion sync; testing; API export; changelog; version; samples; formatting; release metadata. WHEN: create new package version for Azure.Search.Documents; regenerate Azure.Search.Documents; fix Azure.Search.Documents bug; release Azure.Search.Documents; update Azure.Search.Documents spec. Do not use for Azure.ResourceManager.Search or Azure.Provisioning.Search.
search-documents-version-diff
Diff the current Azure.Search.Documents public API surface against a previous published version and detect preview-to-preview regressions where the SDK customization layer was not bubbled up after a TypeSpec change. Use whenever the user asks to compare Azure.Search.Documents betas, verify no Azure.Search.Documents preview features dropped, regression audit between Azure.Search.Documents versions, sanity-check a release branch for Azure.Search.Documents, or investigate a missing Azure.Search.Documents preview feature — even if they don't say the word "diff". Specifically catches dropped wrappers (QueryAnswer/QueryCaption/QueryRewrites style), lost SearchOptions aggregator redirectors, `@@access("internal")` flips, deleted-instead-of-gated `#if AZURE_SEARCH_PREVIEW` blocks, dropped `ServiceVersion` enum values, and convenience-to-protocol downgrades.
search-documents-typespec-validation
TypeSpec validation skill for Azure.Search.Documents SDK. Performs a COMPLETE validation of ALL operations, ALL models, ALL enums, and ALL properties against the TypeSpec definition at any pinned commit. Works for any API version. Generates a full gap report: missing features, extra features, naming mismatches, and recommended fix location. WHEN: "validate Azure.Search.Documents SDK against TypeSpec", "detect Azure.Search.Documents typespec feature gaps", "what is missing from the Azure.Search.Documents SDK", "compare Azure.Search.Documents SDK to spec", "full spec coverage audit for Azure.Search.Documents". Do NOT use for version-to-version diff or regression detection — use search-documents-version-diff instead.
test-skill_file
Roll dice using a random number generator.
roll-dice
Roll dice using a random number generator. Use when asked to roll a die (d6, d20, etc.), roll dice, or generate a random dice roll.