agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-sdk-for-rust/.github/skills/create-hotfix/SKILL.md

create-hotfix

Skill887 starsChanged 29 days agoMITView on GitHub

Create a hotfix (patch) release branch for an Azure SDK Rust crate.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the bundled script for deterministic discovery and git operations.

    line 8
  2. Distinctive:

    Use a single-select prompt to ask the user which crate to patch, using the crate names from the JSON output.

    line 16
  3. Distinctive:

    If candidates were returned, prompt the user with a multiselect containing each candidate's SHA and deterministic summary.

    line 27
  4. Distinctive:

    If commits are selected, preserve their displayed order and run:

    line 30
  5. Very specific:

    If the JSON result has a waiting status, prompt the user to resolve and stage the listed conflicts.

    line 43
  6. Very specific:

    Only show the final message after the script returns a complete status.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a Hotfix

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

  1. 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.

  2. 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.

  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:

    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.

  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 for more information.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free