azd-publish SKILL.md skillA
azd-publish from microsoft/waza is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add microsoft/waza/azd-publish@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- microsoft/waza
- Path
.github/skills/azd-publish/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Feb 28, 2026
- First version recorded
- Feb 12, 2026
- Size
- 6,236 bytes
- Repository stars
- 1,424
- License
- MIT
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).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
…Read the whole file at its exact version.
How to install
mdr add microsoft/waza/azd-publish@sha256:73ad536961557b54The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_s6ozyy3by2iwsyf2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 12, 2026 and Feb 28, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-02-28 | 56f8d37 | 6,236 B | A | view · diff |
| v1.0 | 2026-02-12 | b555179 | 6,232 B | A | view · diff |
| v1.0 | 2026-02-12 | bfccad1 | 5,782 B | A | view · diff |
| v1.0 | 2026-02-12 | b499693 | 5,704 B | A | view · diff |
| v1.0 | 2026-02-12 | ecc7bdc | 5,603 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6236 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
microsoft/waza · 1,424 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s6ozyy3by2iwsyf2 GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/waza/azd-publish GET https://markdownregistry.com/api/v1/blob/73ad536961557b547cb474cb7ccadb4749f407b9f1d8174ca1fd50e59a43da55
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.