How do I install the Changelog skill?

Run npx skillmds@latest add jnmetacode/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.

What does the Changelog skill do?

Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…". It is listed under Coding & Dev Tools on SkillMD.

Is Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. 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. This skill is licensed under MIT.

Who published Changelog?

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

Changelog by jnmetacode — Agent Skill

Name: Changelog
Author: jnMetaCode

File contents

changelog

A changelog is for users deciding whether to upgrade, not a commit dump. Format: Keep a Changelog + semver sections.

Procedure

Find the range. Last release tag: git describe --tags --abbrev=0. Collect commits since: git log <tag>..HEAD --oneline --no-merges.
Bucket each commit:
- Added (feat) · Fixed (fix) · Changed (behavior changes, perf)
- Deprecated · Removed · Security
- Drop pure chore/ci/test/docs noise unless user-visible.
Rewrite each line user-first. Translate implementation into impact:
- commit: fix(ingest): treat mtime regressions as edits
- entry: Fixed duplicate chunks after restoring files from backup. One line each; link the PR/issue number when the repo uses them.
Squash threads. Five commits iterating on one feature = one entry.
Pick the version bump from the buckets: breaking → major, Added → minor, only Fixed → patch (pre-1.0: breaking → minor).

Write the section at the top of CHANGELOG.md:

## [0.2.0] - 2026-06-10
### Added
- Live re-indexing: `engram watch` picks up edits automatically.
### Fixed
- Duplicate chunks after restoring files from backup.

Keep an ## [Unreleased] section at the very top for changes landing between releases; releasing = renaming it and starting a fresh one.

Quality bar

Every entry answers: what can I do now / what stopped being broken? If an entry needs the source code to make sense, rewrite it.

Frequently asked questions

Changelog