Azure Developer CLI (azd) is a command-line tool for building, deploying, and operating applications on Azure. Developers use it to move through application workflows such as coding, building, deployment, and monitoring with Azure templates and resources. Its catalogue entries help AI agents work with azd and Azure application projects.
Borrowing it
Nothing to install: this file belongs to Azure/azure-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-dev/main/.github/skills/changelog-generation/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-devWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/azure/azure-dev/changelog-generation)<a href="https://agentmods.dev/skills/azure/azure-dev/changelog-generation"><img src="https://agentmods.dev/badge/skills/azure/azure-dev/changelog-generation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/azure/azure-dev/changelog-generation"><img src="https://agentmods.dev/badge/skills/azure/azure-dev/changelog-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00167 | $0.01932 |
| Opus 5.5 | $0.00067 | $0.00773 |
| Sonnet 5.5 | $0.00033 | $0.00386 |
| Haiku 4.5 | $0.00017 | $0.00193 |
Grade A, and why
changelog-generation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
changelog-generation
WORKFLOW SKILL — Generates release changelog entries for azd core or extensions.
INVOKES: GitHub MCP tools, git CLI, gh CLI, cspell CLI, ask_user.
Workflow
Step 1 — Determine Scope
Auto-detect scope from the current working directory:
-
Check if the cwd is inside a
cli/azd/extensions/<name>/directory.- If yes → infer extension scope, with
<name>as the target extension. - If no → infer core scope.
- If yes → infer extension scope, with
-
Present the detected scope to the user for confirmation via
ask_user:I detected you're in
<cwd>, so I'll generate changelog for [core azd CLI | extension<name>]. Is that correct?Choices:
- Yes, that's correct (Recommended)
- No, switch to [core | an extension]
-
If extension and not auto-detected: list folders under
cli/azd/extensions/and ask the user to select the target. -
After extension scope is confirmed (whether auto-detected or manually selected), verify the target extension contains
CHANGELOG.md,version.txt, andextension.yaml. If any are missing, stop and list which files are absent.
Step 2 — Find Cutoff & List Commits
Per references/scope-rules.md § Commit Discovery.
- Inspect changelog git history to find the cutoff commit SHA.
- List commits from cutoff to origin/main (extensions: scoped to extension path).
- If >30 commits in the range, display the count and ask the user if they want to see the full list or proceed directly to PR processing.
- Present the commit list to the user. This is a manual pre-filter opportunity — ask if any commits should be explicitly included or excluded before automated processing.
Step 3 — Process Each PR
For each commit remaining after the user's pre-filter in Step 2, extract its PR number using the rules in references/pr-processing.md (each commit maps to exactly one canonical PR). Apply the automated exclusion rules and complete the full sub-workflow before moving to the next. Do not batch or abbreviate — and do not skip a PR unless an explicit error-handling rule applies and the user confirms skipping.
What ships with it
47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- audit/.gitignore 6 B
- audit/corrected/1.22.2.md 687 B
- audit/corrected/1.22.3.md 383 B
- audit/corrected/1.22.4.md 787 B
- audit/corrected/1.22.5.md 405 B
- audit/corrected/1.23.0.md 2.6 KB
- audit/corrected/1.23.1.md 1.0 KB
- audit/corrected/1.23.10.md 305 B
- audit/corrected/1.23.11.md 2.6 KB
- audit/corrected/1.23.12.md 1.0 KB
- audit/corrected/1.23.13.md 2.7 KB
- audit/corrected/1.23.14.md 3.3 KB
- audit/corrected/1.23.15.md 3.5 KB
- audit/corrected/1.23.2.md 617 B
- audit/corrected/1.23.3.md 335 B
- audit/corrected/1.23.4.md 1.1 KB
- audit/corrected/1.23.5.md 604 B
- audit/corrected/1.23.6.md 1.7 KB
- audit/corrected/1.23.7.md 3.9 KB
- audit/corrected/1.23.8.md 4.0 KB
- audit/corrected/1.23.9.md 3.2 KB
- audit/findings.md 12 KB
- audit/go.mod 59 B
- audit/main.go 29 KB
- audit/published/1.22.2.md 687 B
- audit/published/1.22.3.md 383 B
- audit/published/1.22.4.md 787 B
- audit/published/1.22.5.md 405 B
- audit/published/1.23.0.md 2.7 KB
- audit/published/1.23.1.md 1.0 KB
- audit/published/1.23.10.md 305 B
- audit/published/1.23.11.md 2.6 KB
- audit/published/1.23.12.md 1.0 KB
- audit/published/1.23.13.md 3.2 KB
- audit/published/1.23.14.md 3.7 KB
- audit/published/1.23.15.md 3.5 KB
- audit/published/1.23.2.md 617 B
- audit/published/1.23.3.md 335 B
- audit/published/1.23.4.md 1.2 KB
- audit/published/1.23.5.md 604 B
- audit/published/1.23.6.md 1.7 KB
- audit/published/1.23.7.md 3.9 KB
- audit/published/1.23.8.md 4.0 KB
- audit/published/1.23.9.md 3.2 KB
- audit/README.md 2.6 KB
- references/pr-processing.md 5.1 KB
- references/scope-rules.md 3.4 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 29d ago Changed 1eb797e7857f
- 1mo ago First seen · 116 lines · 167 tokens per session scan A 63bd077cbb8e
changelog-generation is a skill published in the GitHub repository Azure/azure-dev (570 stars, last pushed today), licensed MIT. It adds 167 tokens to every session and 1,932 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.