update-changelog — Claude Code skill: automate release notes
update-changelog is a Claude Code skill that builds formatted CHANGELOG entries from commits between the latest release tag and the current version.
Apache-2.0 130 installs ★ 3,224 updated 2026-09-27
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a claude-codeWhat update-changelog does
The skill detects your most recent git tag as the baseline, retrieves all commits since then, filters for user-facing changes (features, fixes, breaking changes), and adds them to an Unreleased section in CHANGELOG.md or CHANGELOG. If the section doesn't exist, it creates one matching the existing file style.
Each entry follows changelog conventions: past-tense verb or noun phrase, code in backticks, pull request numbers without commit hashes. Insignificant changes—typos, internal refactoring, minor doc tweaks—are skipped automatically.
You need git with tag and history access. The skill respects non-standard default branch names instead of assuming main.
What it helps with
- extract release history from git without manually reviewing commits
- add new entries to CHANGELOG in consistent format
- separate user-facing changes from refactoring and documentation edits
- keep version notes in sync with actual repository history
Example prompts for the agent
- Update the CHANGELOG with all commits since the last tag
- Add recent features and bug fixes to CHANGELOG.md under Unreleased
- Read the git log from version 2.12.0 and populate the changelog section
How to install update-changelog
1Skills CLI (Vercel)
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a claude-code2Manually: put the files in place
~/.claude/skills/update-changelog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/update-changelog/
1Skills CLI (Vercel)
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a codex2Manually: put the files in place
.agents/skills/update-changelog/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a cursor2Manually: put the files in place
.cursor/skills/update-changelog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mitsuhiko/agent-stuff skills/update-changelog2Manually: put the files in place
.github/skills/update-changelog/SKILL.md1Skills CLI (Vercel)
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a gemini-cli2Platform CLI
gemini skills install https://github.com/mitsuhiko/agent-stuff --path skills/update-changelogManually: put the files in place
.devin/skills/update-changelog/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mitsuhiko/agent-stuff --skill update-changelog -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about update-changelog
How do I install update-changelog in Claude Code?
Run npx skills add mitsuhiko/agent-stuff --skill update-changelog -a claude-code, then open ~/.claude/skills/update-changelog/SKILL.md to verify installation.
What does update-changelog do?
The skill analyzes commits between your latest git tag and HEAD, identifies notable changes (features, fixes, breaking changes), and adds them to the Unreleased section of your CHANGELOG with pull request references in the correct format.
Which changes does the skill skip?
It skips typo fixes, internal refactoring, and minor documentation updates. It focuses on changes that matter to users: new features, bug fixes, and breaking changes.
Source text
SKILL.md · Apache-2.0
--- name: update-changelog description: "Read this skill before updating changelogs" --- Update the repository changelog with changes between the last release and the current version (`main`) that are not yet incorporated. If `CHANGELOG.md` does not exist, use `CHANGELOG` instead. ## Step-by-Step Process ### 1. Determine baseline version If no baseline version is provided, use the most recent git tag. You can find it with `git describe --tags --abbrev=0`. ### 2. Find the commits from git Use the following commands to gather commit information: ```bash # Get the baseline version (if not provided) git describe --tags --abbrev=0 # Get all commits since the baseline version git log <baseline-version>..HEAD ``` ### 3. Update the changelog Read the existing changelog file (`CHANGELOG.md`, or `CHANGELOG` if missing) and check if there are changes not yet incorporated, then add them. Always add them to the "Unreleased" section only. If there is none yet, add it at the top in the same style as the existing changelog (for example, `## Unreleased` vs `## [Unreleased]`). ## Ground Rules When Writing Changelogs ### Content Guidelines * Focus on **notable changes** that affect users (features, fixes, breaking changes) * Mention pull requests (`#NUMBER`) when available, but not raw commit hashes * Ignore insignificant changes (typo fixes, internal refactoring, minor documentation updates) * Group related changes together when appropriate * Order entries by importance: breaking changes first, then features, then fixes ### Style Guidelines * Use valid markdown syntax * Start each entry with a past-tense verb or descriptive phrase * Keep entries concise but descriptive enough to understand the change * Use bullet points (`*` or `-`) for individual changes * Format code references with backticks (e.g., `` `foo.cleanup` ``) ### Example Format ```markdown ## 2.13.0 * Added multi-key support to the `|sort` filter. #827 * Fix `not undefined` with strict undefined behavior. #838 * Added support for free threading Python. #841 ## 2.12.0 * Item or attribute lookup will no longer swallow all errors in Python. #814 * Added `|zip` filter. #818 * Fix `break_on_hyphens` for the `|wordwrap` filter. #823 * Prefer error message from `unknown_method_callback`. #824 * Ignore `.jinja` and `.jinja2` as extensions in auto escape. #832 ``` ### Good vs. Bad Examples **Good:** * `Fixed an issue with the TypeScript SDK which caused an incorrect config for CJS.` * `Added support for claim timeout extension on checkpoint writes.` * `Improved error reporting when task claim expires.` **Bad:** * `Fixed bug` (too vague) * `Updated dependencies` (insignificant unless it fixes a security issue) * `Refactored internal code structure` (internal change, not user-facing) * `Fixed typo in comment` (insignificant) ## Notes * If the current changelog already has an "Unreleased" section with content, append to it rather than replacing it * Preserve the existing changelog style and formatting (headings, bullet style, ordering, and spacing) * If the repo uses a different default branch name, treat that as the "current version" instead of `main` * When in doubt about whether a change is significant, err on the side of including it
© mitsuhiko · Apache-2.0 · mitsuhiko/agent-stuff