// Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
| name | update-changelog |
| description | Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent. |
| argument-hint | Describe the target, for example: latest version only |
Update docs/CHANGELOG.md from repository evidence instead of guesswork.
docs/CHANGELOG.mdFeatures / Improvements / Bug Fixes headings when the release only has a few clear itemsdocs/CHANGELOG.mdpackage.json version and compare it with the top changelog entryPrefer these sources in order:
GH_PAGER=cat gh release view v<version> --repo <owner>/<repo> --json tagName,name,publishedAt,body
git log -1 --format=%cs v<version>
git --no-pager log --format='%h %s' --no-merges v<previous>..v<version>
git --no-pager diff --name-only v<previous>..v<version>
git --no-pager diff --stat v<previous>..v<version>
Include:
Exclude unless explicitly requested:
### Features, ### Improvements, and ### Bug Fixes