Changelog

Skill sp-daewoon/chronicle/skills/changelog

📜 Never write changelogs or release notes by hand again — automate your entire docs lifecycle (ADR · changelog · release · devlog · index) with 6 zero-dependency Claude Code skills.

Install

npx -y skills add sp-daewoon/chronicle --skill changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Keep a changelog humans actually read, and never hand-edit version sections again. Use when adding a change entry or promoting unreleased work into a released version. Follows the Keep a Changelog standard, appends entries chronologically, stays merge-conflict-resistant, and runs with zero dependencies on any repo.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.3 KB, as published. Nobody here has run it

Changelog Workflow

Maintain a Keep a Changelog formatted file.

Add an entry

Pick the correct type — one of: Added, Changed, Deprecated, Removed, Fixed, Security.

node "${CLAUDE_PLUGIN_ROOT}/scripts/changelog-parse.mjs" add --type Added --text "Describe the change in one line"

This inserts the line under ## [Unreleased] > ### <Type>, creating the file or subsection if needed.

Promote a version (at release time)

node "${CLAUDE_PLUGIN_ROOT}/scripts/changelog-parse.mjs" release --version 1.2.0 --date 2026-05-31

This moves everything under [Unreleased] into a new ## [1.2.0] - 2026-05-31 section and leaves a fresh empty [Unreleased] on top.

Rules

One entry = one user-facing line. Write for humans, not commit hashes.
Use today's real date for --date (never guess).
Run this before tagging a release so the release skill can read the new section.