Official agent skill

waza azd Extension Publisher

Walks through releasing a new version of the waza azd extension: changelog from commits, semver bump with your confirmation, and a release PR.

OfficialMITAuto-check passedDevelopment

Install waza azd Extension Publisher

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install microsoft/waza azd-publish --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azd-publish .claude/skills/azd-publish && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .claude/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microsoft/waza azd-publish --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azd-publish .agents/skills/azd-publish && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .agents/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microsoft/waza azd-publish --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azd-publish .cursor/skills/azd-publish && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .cursor/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/microsoft/waza.git --path .github/skills/azd-publish

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microsoft/waza azd-publish --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azd-publish .gemini/skills/azd-publish && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .gemini/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install microsoft/waza azd-publish

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azd-publish .github/skills/azd-publish && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .github/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/waza --skill azd-publish -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microsoft/waza azd-publish --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/waza.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azd-publish .opencode/skills/azd-publish && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "azd-publish" agent skill from https://github.com/microsoft/waza/tree/main/.github/skills/azd-publish into .opencode/skills/azd-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azd-publish", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: azd-publish
GitHub stars: 1.4k
Token cost: ~1.5k tokens
SKILL.md length: 573 words
Files: 1
Skills in repo: 16
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Walks through releasing a new version of the waza azd extension: changelog from commits, semver bump with your confirmation, and a release PR.

Works in 5 steps: Gather Changes and Update Changelog → Determine Version → Update Version Files → …
Preparing a new release of the waza azd extension
SKILL.md covers When to Use, Workflow, File Reference and Important Notes
Calls git and gh

What it does

The skill automates a release of the waza azd extension step by step and asks you at every decision point. It reads the current version from version.txt and extension.yaml, flags a mismatch, and collects commits since the last release tag, grouping them into Added for feat commits, Fixed for fix commits, Changed for refactor, chore and docs commits, and Removed for removals, then shows the summary for review.

It stages the changelog in Keep a Changelog format, moving Unreleased items or filling them from the git log. Then it recommends a major, minor or patch bump from the commit types, with reasoning such as the count of feature commits and the absence of breaking changes, and asks you to confirm or pick another before computing the new version and finalizing the changelog headers and comparison links. The workflow ends with a release PR for review. Running evals, writing skills and CI pipeline changes are handled elsewhere.

When your agent uses it

Preparing a new release of the waza azd extension
Bumping the extension version and updating CHANGELOG.md
Opening a release PR for review

Example prompts

“Prepare a new release of the waza azd extension.”
“Bump the version and update the changelog since the last release.”
“Recommend the right semver bump for the commits since the last tag.”

Requirements

A checkout of the waza repository with version.txt, extension.yaml and CHANGELOG.md

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Gather Changes and Update Changelog
Determine Version
Update Version Files
Review Changes
Ask About PR Creation

What it can do on your machine

Read from SKILL.md and the folder at commit 774df00. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- keepachangelog.com
- semver.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

waza azd Extension Publisher loads about 1.5k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 573 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~95
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/waza at commit 774df00, republished under its MIT licence (© microsoft). 573 words, ~1,510 tokens.

Download SKILL.mdSave it as .claude/skills/azd-publish/SKILL.md (or your agent's skills folder).

name: azd-publish
description: Prepare and publish a new version of the waza azd extension. USE FOR: "publish extension", "release new version", "bump version", "prepare release", "update changelog", "azd publish", "new release", "version bump", "cut a release". DO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring), CI/CD pipeline changes (edit workflow files directly).
metadata.author: spboyer
metadata.version: 1.0

azd Extension Publish

Automate version bumps, changelog updates, and PR creation for waza azd extension releases.

When to Use

Preparing a new release of the waza azd extension
Bumping the version number (major, minor, or patch)
Updating the changelog with changes since last release
Creating a release PR for review

Workflow

Follow these steps in order. Ask the user for input at each decision point.

Step 1: Gather Changes and Update Changelog

Get the current version from version.txt and extension.yaml, then collect commits since the last release:

bash

cat version.txt

# Find the latest azd extension version tags
git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -5

# Get commits since last azd extension tag
last_tag=$(git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -1)
git log "${last_tag}..HEAD" --oneline --no-decorate

If version.txt and extension.yaml differ, flag it to the user before proceeding.

Summarize the changes grouped by type:

Added — feat: commits
Fixed — fix: commits
Changed — refactor:, chore:, docs: commits
Removed — any removal-related commits

Present the summary to the user for review.

Then update CHANGELOG.md. The changelog follows Keep a Changelog format.

Perform these updates (using a placeholder version X.Y.Z — the actual version is determined in Step 2):

Move Unreleased content: Move any items currently under ## [Unreleased] into a staging area. If [Unreleased] is empty, populate from the git log summary gathered above.
Populate from commits: Prepare entries grouped under ### Added, ### Fixed, ### Changed as appropriate based on the commits gathered above.

Hold these changelog entries — the new version section header and comparison links will be finalized after the version is determined in Step 2.

Step 2: Determine Version

Based on the changes gathered in Step 1, recommend a version bump type using standard semver semantics:

major — Breaking changes, removals of public API (feat!:, BREAKING CHANGE:) → (MAJOR+1).0.0
minor — New features, backward compatible (feat:) → MAJOR.(MINOR+1).0
patch — Bug fixes, docs, refactors, chores (fix:, docs:, refactor:, chore:) → MAJOR.MINOR.(PATCH+1)

Present the recommendation with rationale (e.g., "I see 3 feat: commits and no breaking changes — recommending a minor bump").

ASK THE USER to confirm the recommended bump or choose a different one.

Compute the new version and confirm with the user before proceeding.

Then finalize the changelog:

Create new version section: Insert a new section below ## [Unreleased] with today's date:
markdown
```
## [X.Y.Z] - YYYY-MM-DD
```
Add the prepared entries from Step 1 under the new version section.

Update comparison links at the bottom of the file:

markdown

[Unreleased]: https://github.com/microsoft/waza/compare/azd-ext-microsoft-azd-waza_X.Y.Z...HEAD
[X.Y.Z]: https://github.com/microsoft/waza/compare/azd-ext-microsoft-azd-waza_PREVIOUS...azd-ext-microsoft-azd-waza_X.Y.Z

Clear the Unreleased section: Leave ## [Unreleased] with empty subsections or blank.

Show full SKILL.md (267 more words)Show less

Step 3: Update Version Files

Update these files with the new version:

version.txt — Replace contents with new version string
extension.yaml — Update the version: field

Step 4: Review Changes

Show the user a summary of all changes made:

New version number
Files modified: version.txt, extension.yaml, CHANGELOG.md
Show the diff with git diff

Step 5: Ask About PR Creation

ASK THE USER: Should I create a PR with these changes?

If yes:

Create a feature branch:
bash
```
git checkout -b release/v{VERSION}
```

Stage and commit all changes:

bash

git add version.txt extension.yaml CHANGELOG.md
git commit -m "chore: Prepare release v{VERSION}"

Push the branch:
bash
```
git push origin release/v{VERSION}
```

Create a PR using the GitHub CLI:

bash

gh pr create \
  --title "Release v{VERSION}" \
  --body "## Release v{VERSION}

### Changes
{changelog entries for this version}

### Checklist
- [ ] Version bumped in version.txt and extension.yaml
- [ ] CHANGELOG.md updated
- [ ] CI passes
- [ ] Ready to publish via 'Publish azd Extension' workflow" \
  --base main \
  --head release/v{VERSION}

If no:

Leave the changes uncommitted in the working tree
Inform the user they can review and commit manually

File Reference

File	Purpose	What Gets Updated
`version.txt`	Single source of version truth	New semver version string
`extension.yaml`	azd extension manifest	`version:` field
`CHANGELOG.md`	Human-readable change history	New version section with entries

Important Notes

Always use conventional commit prefixes (feat:, fix:, chore:, docs:, refactor:) when interpreting git history
The changelog format must follow Keep a Changelog
Version numbering must follow Semantic Versioning
The PR branch naming convention is release/v{VERSION}
After the PR is merged, the user should trigger the Publish azd Extension workflow (azd-ext-release.yml) to build, pack, and publish the extension

Files

Just SKILL.md in .github/skills/azd-publish of microsoft/waza.

Open the folder on GitHubat commit 774df00

Compare with similar skills

waza azd Extension Publisher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

waza azd Extension Publisher compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
waza azd Extension Publisher this skillmicrosoft/waza	1.4k	—	~1.5k	Automated safety check: Pass	MIT	2 days ago
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	yesterday
Worktrunk Release Workflowmax-sixty/worktrunk	9k	—	~6.9k	Automated safety check: Pass	Custom licence	today
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
ClawRouter Release ChecklistBlockRunAI/ClawRouter	6.6k	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Release PreparationCherryHQ/cherry-studio	52k	—	~4.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
9k GitHub stars~6.9k tokensUpdated today
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
6.6k GitHub stars~1.4k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
52k GitHub stars~4.3k tokensUpdated today
DevelopmentAuto-check passed
Codex Proxy RS Release
zyycn/codex-proxy-rs
Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.
750 GitHub stars~327 tokensUpdated today
DevelopmentAuto-check passed

Questions about waza azd Extension Publisher

What does waza azd Extension Publisher do?

Walks through releasing a new version of the waza azd extension: changelog from commits, semver bump with your confirmation, and a release PR. The skill automates a release of the waza azd extension step by step and asks you at every decision point.yaml, flags a mismatch, and collects commits since the last release tag, grouping them into Added for feat commits, Fixed for fix commits, Changed for refactor, chore and docs commits, and Removed for removals, then shows the summary for review.

When should I use waza azd Extension Publisher?

waza azd Extension Publisher fits situations like: preparing a new release of the waza azd extension; bumping the extension version and updating CHANGELOG.md; opening a release PR for review.

How do I install waza azd Extension Publisher in Claude Code?

Run `npx skills add microsoft/waza --skill azd-publish -a claude-code`. Or copy the skill folder (.github/skills/azd-publish in microsoft/waza) into .claude/skills/azd-publish in your project. Claude Code loads it when a task matches its description.

How do I install waza azd Extension Publisher in Codex?

Run `npx skills add microsoft/waza --skill azd-publish -a codex`. Or copy the skill folder (.github/skills/azd-publish in microsoft/waza) into .agents/skills/azd-publish in your project. Codex loads it when a task matches its description.

Can I use waza azd Extension Publisher in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/waza --skill azd-publish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azd-publish, .gemini/skills/azd-publish, .github/skills/azd-publish and .opencode/skills/azd-publish in your project.

What does waza azd Extension Publisher need to run?

Going by SKILL.md and its folder, waza azd Extension Publisher needs the command-line tools its instructions call (git and gh). Our summary lists: A checkout of the waza repository with version.txt, extension.yaml and CHANGELOG.md.

Does waza azd Extension Publisher access the network?

SKILL.md names 2 domains. As links in the text: keepachangelog.com and semver.org. This is read from the text; nothing was executed.

Is waza azd Extension Publisher safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does waza azd Extension Publisher use?

waza azd Extension Publisher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does waza azd Extension Publisher use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to waza azd Extension Publisher?

Skills that share tags, products or a category with waza azd Extension Publisher: Hunk Release Workflow (modem-dev/hunk, 9.5k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains waza azd Extension Publisher?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/waza, which has 1,403 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.

Source: microsoft/waza on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install waza azd Extension Publisher

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

azd Extension Publish

When to Use

Workflow

Step 1: Gather Changes and Update Changelog

Step 2: Determine Version

Step 3: Update Version Files

Step 4: Review Changes

Step 5: Ask About PR Creation

File Reference

Important Notes

Files

Compare with similar skills

Similar skills

More from microsoft/waza

Related

Questions about waza azd Extension Publisher