How do I install the Create Hotfix skill?

Run npx skillmds@latest add azure-azure-sdk-for-rust/create-hotfix in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Create Hotfix skill do?

Create a hotfix (patch) release branch for an Azure SDK Rust crate. It is listed under DevOps & Infra on SkillMD.

Is Create Hotfix safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Hotfix?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Hotfix free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Hotfix?

Azure (@azure-azure-sdk-for-rust) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Hotfix by azure-azure-sdk-for-rust

Name: Create Hotfix
Rating: 4.666666666666667 (3 reviews)
Author: Azure

File contents

Create a Hotfix

Use the bundled script for deterministic discovery and git operations. Run all commands from the repository root.

List workspace crates:
```
python3 .github/skills/create-hotfix/create_hotfix.py list-crates
```
Use a single-select prompt to ask the user which crate to patch, using the crate names from the JSON output.
Prepare the hotfix:
```
python3 .github/skills/create-hotfix/create_hotfix.py prepare <crate-name>
```
The command fetches tags and main directly from https://github.com/Azure/azure-sdk-for-rust, finds the latest stable <crate-name>@<version> tag, calculates the next patch version, creates hotfix/<crate-name>-<version> from that tag unless already on a hotfix/ branch, and returns candidate commits from main as JSON.
If candidates were returned, prompt the user with a multiselect containing each candidate's SHA and deterministic summary. Allow selecting none.
If commits are selected, preserve their displayed order and run:
```
python3 .github/skills/create-hotfix/create_hotfix.py cherry-pick <sha>...
```
The script automatically resolves Cargo.lock conflicts by taking --ours, then regenerating it with:
```
cargo generate-lockfile --manifest-path Cargo.toml
```
If the JSON result has a waiting status, prompt the user to resolve and stage the listed conflicts. Remain waiting for the user to confirm they are ready, then run:
```
python3 .github/skills/create-hotfix/create_hotfix.py continue
```
Repeat this step if another commit conflicts. Do not abort or skip commits. Only show the final message after the script returns a complete status.
Report the selected crate, base tag, patch version, branch, and cherry-picked commits. Tell the user:

Make any additional hotfix changes on this branch. Do not merge this branch into main; cherry-pick any new fixes into main separately. See the Azure SDK hotfix branch policy for more information.

---name: create-hotfixdescription: Create a hotfix (patch) release branch for an Azure SDK Rust crate.---# Create a HotfixUse the bundled script for deterministic discovery and git operations. Run all commands from the repository root.1. List workspace crates: ```bash python3 .github/skills/create-hotfix/create_hotfix.py list-crates ``` Use a single-select prompt to ask the user which crate to patch, using the crate names from the JSON output.2. Prepare the hotfix: ```bash python3 .github/skills/create-hotfix/create_hotfix.py prepare <crate-name> ``` The command fetches tags and `main` directly from `https://github.com/Azure/azure-sdk-for-rust`, finds the latest stable `<crate-name>@<version>` tag, calculates the next patch version, creates `hotfix/<crate-name>-<version>` from that tag unless already on a `hotfix/` branch, and returns candidate commits from `main` as JSON.3. If candidates were returned, prompt the user with a multiselect containing each candidate's SHA and deterministic summary. Allow selecting none.4. If commits are selected, preserve their displayed order and run: ```bash python3 .github/skills/create-hotfix/create_hotfix.py cherry-pick <sha>... ``` The script automatically resolves `Cargo.lock` conflicts by taking `--ours`, then regenerating it with: ```bash cargo generate-lockfile --manifest-path Cargo.toml ``` If the JSON result has a `waiting` status, prompt the user to resolve and stage the listed conflicts. Remain waiting for the user to confirm they are ready, then run: ```bash python3 .github/skills/create-hotfix/create_hotfix.py continue ``` Repeat this step if another commit conflicts. Do not abort or skip commits. Only show the final message after the script returns a `complete` status.5. Report the selected crate, base tag, patch version, branch, and cherry-picked commits. Tell the user: > Make any additional hotfix changes on this branch. Do not merge this branch > into `main`; cherry-pick any new fixes into `main` separately. See the > [Azure SDK hotfix branch policy](https://azure.github.io/azure-sdk/policies_repobranching.html#hotfix-branches) > for more information.

Frequently asked questions

Create Hotfix