changelog-managerlisted

# Changelog Manager When invoked, perform the following changelog management tasks: analyze git history and help update CHANGELOG.md with well-written entries for the `[Unreleased]` section. ## Workflow Execute these steps in order: ### Step 1: Find and Read CHANGELOG.md 1. Look for `CHANGELOG.md` in the repository root: ```bash ls -la CHANGELOG.md ``` 2. If not found, check common locations or ask the user: - `docs/CHANGELOG.md` - `CHANGES.md` 3. Read the changelog and identify: - The last released version (e.g., `## [0.2.0]`) - Existing entries under `## [Unreleased]` - The changelog format and style used If no CHANGELOG.md exists, ask the user if they want you to create one. ### Step 2: Get Git History Since Last Release (Enhanced) **Path filter note:** If a path filter is provided in the prompt (e.g., `-- agent-alchemy/sdd/`), append it to all `git log` commands in this step to scope results to that sub-project. 1. Find the tag for the last release: ```bash git tag --list 'v*' --sort=-version:refname | head -5 ``` 2. Get commits with extended format including body (for breaking change notices): ```bash git log v{version}..HEAD --format="%H|%s|%b" --no-merges [path_filter] ``` If no tags exist, get recent commits with warning: ```bash git log --format="%H|%s|%b" --no-merges -50 [path_filter] ``` 3. Extract PR/issue references for later enrichment: ```bash git log v{version}..HEAD --no-merges --onelin