changelog-generation

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:

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

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

3. If extension and not auto-detected: list folders under cli/azd/extensions/ and ask the user to select the target.

4. After extension scope is confirmed (whether auto-detected or manually selected), verify the target extension contains CHANGELOG.md, version.txt, and extension.yaml. If any are missing, stop and list which files are absent.

Step 2 — Determine Version & Update Files

Files to update (core): cli/azd/CHANGELOG.md, cli/version.txt, cli/azd/pkg/azdext/version.go Files to update (extension): <extension>/CHANGELOG.md, <extension>/version.txt, <extension>/extension.yaml

For version derivation rules, see references/scope-rules.md § Version Files.

• Core: use the version specified in the triggering issue or user request if explicit (e.g., "Create changelog for 1.24.2"); otherwise derive from the existing unreleased header (strip -beta.* and (Unreleased)), use today's date. Update cli/version.txt and cli/azd/pkg/azdext/version.go (Version constant) to the released version.
• Extension: ask the user for the new version number via ask_user. Update both version.txt and extension.yaml — they must match exactly.