azsdk-common-prepare-release-plan

Create, update, and manage Azure SDK release plan work items via MCP tools.

2.6k|2.2k|Updated Dec 6, 2011

Search Tags:#release management #work item #release plan #typespec #azure sdk #MCP Tools #spec pr

Ready to run

npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-prepare-release-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azsdk-common-prepare-release-plan
Source: https://github.com/Azure/azure-sdk-for-java/tree/main/.github/skills/azsdk-common-prepare-release-plan
Command: npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-prepare-release-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating an Azure SDK release requires tracking release plan work items, linking spec PRs and SDK pull requests, and validating release types, which is error-prone when done manually across Azure DevOps and GitHub.

Core Features & Use Cases

Release Plan Lifecycle: Create, retrieve, update, and abandon release plans tied to TypeSpec projects or API spec PRs.
PR Linking: Link SDK pull requests per language and attach namespace approval issues for first management plane releases.
Validation Rules: Enforce correct spec PR repository pairing with API release type (Private Preview vs Public Preview/GA) and proper date formats.
Use Case: A developer with a merged spec PR in Azure/azure-rest-api-specs asks to create a GA release plan for June 2026, then links their Java SDK PR once generated.

Quick Start

Ask the agent to create a release plan for your TypeSpec project path, providing the target release month, API release type, and SDK release type.

Frequently Asked Questions about azsdk-common-prepare-release-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a release plan for an Azure SDK spec PR?▼

Provide the relative TypeSpec project path, target release month in "Month YYYY" format, API release type (Private Preview, Public Preview, or GA), and SDK release type (beta or stable). The skill checks for an existing plan first, then calls azsdk_create_release_plan.

How do I link an SDK pull request to a release plan?▼

Provide the release plan ID or work item ID, the SDK pull request URL, and the language (e.g., Java, Python, .NET). The skill runs azsdk_link_sdk_pull_request_to_release_plan, repeating for each language PR.

Can I use a work item ID instead of a release plan ID?▼

Yes, the release plan tools accept either a Release Plan ID or an Azure DevOps work item ID. Each tool resolves the value automatically, so no separate lookup call is needed to translate between them.

Why does release plan creation fail with my spec PR?▼

Creation fails if the spec PR repository does not match the API release type: Private Preview requires a PR in azure-rest-api-specs-pr, while Public Preview and GA require azure-rest-api-specs. Verify the Service Tree ID and PR URL as well.

When should I not use this release plan skill?▼

Do not use it for SDK code generation, pipeline troubleshooting, or API review feedback. It only manages release plan work items and their linked PRs through the azure-sdk-mcp server.