changelog-update
Add entries to the Unreleased section of an existing CHANGELOG.md, written in human-readable Keep a Changelog style rather than raw commit-log dumps. Use this when the user wants to update the changelog, log a change they just made, or catch the changelog up with recent commits. Triggers on: "update the changelog", "add this to the changelog", "log this change", "update CHANGELOG.md". All AI steps run on the current Claude session — no OpenAI, no API key.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- changelog-update
- description
- Add entries to the Unreleased section of an existing CHANGELOG.md, written in human-readable Keep a Changelog style rather than raw commit-log dumps. Use this when the user wants to update the changelog, log a change they just made, or catch the changelog up with recent commits. Triggers on: "update the changelog", "add this to the changelog", "log this change", "update CHANGELOG.md". All AI steps run on the current Claude session — no OpenAI, no API key.
03 SKILL.md 正文
changelog-update
Add one or more entries to CHANGELOG.md's Unreleased section. You,
Claude, decide what's worth mentioning and how to phrase it — Keep a
Changelog exists specifically so changelogs read as prose for humans, not as a
dump of git log. A small TypeScript toolbelt CLI does the deterministic
insertion and validation.
The toolbelt CLI
Deterministic operations run through the bundled CLI:
npx @jetienne/changelog.ai <command> [args]
| Command | Purpose |
|---|---|
add -c <Category> -t "<entry>" |
Insert one entry under Unreleased, creating the category if needed. Errors if the exact same entry is already there. |
validate [-i <file>] |
Structurally validate; exits non-zero and lists problems. |
The six categories, in the order they're always rendered: Added, Changed,
Deprecated, Removed, Fixed, Security.
Steps
- Find out what's new. If the user described a specific change, use
that. Otherwise inspect recent history:
- If
CHANGELOG.mdalready has released versions, find the latest one and rungit log v<latest>..HEAD --oneline(drop thevif the project doesn't prefix its tags that way) to see what's landed since. - If there's no release yet, look at the last few commits with
git log --oneline, or just ask the user what to log.
- If
- Write for the reader, not the log. For each change worth mentioning:
- Describe the effect in plain language ("Fixed a crash when the input file is empty"), not the commit message or the diff.
- Skip pure noise (formatting, comment tweaks, internal refactors with no user-visible effect) unless the user asks to include it.
- Pick the right category — a bug fix is
Fixed, a new capability isAdded, a behavior change to something existing isChanged, and so on. - Check the existing
Unreleasedentries first so you don't add a near-duplicate of something already logged.
- Add each entry:
npx @jetienne/changelog.ai add -c Added -t "Support exporting reports to CSV." - Validate + self-correct (see below).
- Summarize what you added (category by category) for the user.
Validate + self-correct (required after every add)
- Run
npx @jetienne/changelog.ai validate. - If it exits non-zero, read each reported problem and fix it — for a structural problem this usually means the file was hand-edited elsewhere; prefer fixing it through the CLI over hand-editing markdown.
- Repeat until it passes.
Notes
- If
CHANGELOG.mddoesn't exist yet, stop and point the user at thechangelog-initskill instead. - Cutting a new version from these entries is the
changelog-releaseskill's job, not this one's.
04 同仓库更多 Skills
changelog-release
Make a new release in CHANGELOG.md: move the Unreleased entries into a dated version section and regenerate the comparison links. Use this when the user wants to make a release, bump the version, or prepare release notes. Triggers on: "make a release", "release version X", "bump the version", "prepare a release". All AI steps run on the current Claude session — no OpenAI, no API key.
changelog-init
Create a new CHANGELOG.md in the Keep a Changelog 1.1.0 format. Use this when the user wants to add a changelog to a project that does not have one yet, or asks to start tracking changes. Triggers on: "create a changelog", "add a CHANGELOG.md", "start a changelog for this project", "set up a changelog". If a CHANGELOG.md already exists, this skill stops and points at the sibling changelog-update skill instead. All AI steps run on the current Claude session — no OpenAI, no API key.
changelog-update
暂无简介
changelog-release
暂无简介
changelog-init
暂无简介