Changelog

changelog

Manage CHANGELOG.md per Keep a Changelog 1.1.0 and SemVer 2.0.0:

• add: one entry;
• from-commits: derive entries from Conventional Commits;
• release: cut a version.

Edit only CHANGELOG.md. Never change version files, commit, or tag; release prints suggested commands.

Step 1 — Resolve the action

Resolve add, from-commits (commits), or release from $ARGUMENTS or the request; ask if ambiguous.

Step 2 — Pre-flight (all actions)

root=$(git rev-parse --show-toplevel 2>/dev/null) || root=.
ls "$root/CHANGELOG.md" 2>/dev/null

Always use $root/CHANGELOG.md, never a cwd-relative path.

• Existing: read and preserve style.
• Missing for add/from-commits: create the standard linked title, intro, and ## [Unreleased] skeleton.
• Missing for release: stop and suggest /changelog add or /changelog from-commits.

Step 3 — Insert under [Unreleased] (add, from-commits)

Append - <imperative description> to its category under [Unreleased], creating the category in canonical order. Never edit released sections or date [Unreleased].

Step 4 — Run the action

Load writing guidelines for entry rules, commit mapping, and SemVer bumps.

• add — use the user's text or ask for one of the six categories and a ≤15-word description; tighten and insert it.
• from-commits — follow the process below.
• release — follow references/release.md.

from-commits