Azsdk Common SDK Release

DevOps & Security

azsdk-common-sdk-release

Azsdk Common SDK Release is an Agent Skill for devops & security published in the Azure/azure-rest-api-specs repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/Azure/azure-rest-api-specs/blob/HEAD/.github/skills/azsdk-common-sdk-release/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/azsdk-common-sdk-release, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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-mcp server; there is no CLI fallback for the release workflow.
Collect packageName and language, 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 packageName and language from the user. Optionally get branch (defaults to main).
Determine Intent — If the user explicitly asks to "check readiness" or "check if ready", run azure-sdk-mcp:azsdk_release_sdk with checkReady: true. Otherwise, proceed to trigger the release directly.
Trigger Release — Run azure-sdk-mcp:azsdk_release_sdk with checkReady: 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-mcp server. No CLI fallback — prompt user to configure MCP if unavailable.