How do I install the Changelog skill?

Run npx skillmds@latest add skillkeel/changelog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changelog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changelog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changelog?

Skillkeel (@skillkeel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changelog by skillkeel — Agent Skill

Name: Changelog
Rating: 4.2 (5 reviews)
Author: Skillkeel

Changelog

Use when the user asks to update or generate CHANGELOG.md, prepare release notes, or cut a version. Builds entries from git history since the last tag (or a given range) in Keep a Changelog format, grouped by change type, never from memory.

Skillkeel Updated Sep 22, 2026

File contents

changelog

Procedure

Find the range: git describe --tags --abbrev=0 → last tag. If no tags, use the first commit or ask. Range = <last-tag>..HEAD.
Collect: git log --no-merges --format='%h %s' <range>. For each commit, read the subject; open the diff only when the subject is unclear (git show --stat <sha>).
Map Conventional Commit types → sections: feat→Added, fix→Fixed, perf/refactor→Changed, deprecate→Deprecated, remove→Removed, security/fix(security)→Security. Ignore chore, ci, test, docs unless user-visible.
Write user-facing lines (what changed for the user, not how). One line per commit or per logical group; reference PR/issue numbers when present in the subject ((#123)).
If CHANGELOG.md exists, insert under ## [Unreleased] (create the heading if missing) without touching older entries. If it does not exist, create it with the Keep a Changelog header.
If the user is cutting a version: rename [Unreleased] → [X.Y.Z] - YYYY-MM-DD, add a fresh empty [Unreleased], and propose (do not run) git tag -a vX.Y.Z -m "...".
Show the diff of CHANGELOG.md.

Rules

Every line traces to a commit in the range. No invented entries.
Breaking changes get a BREAKING: prefix and go first in their section.
Do not bump package.json/pyproject.toml versions unless asked.

Eval

evals/changelog/: fixture with tag v0.1.0 and 5 commits after it (2 feat, 1 fix, 1 chore, 1 feat!: breaking); expected: chore omitted, breaking first with prefix, entries under [Unreleased].

Frequently asked questions