Claude Code Skill for Changelogs Between Git Tags

Read the release range and turn commit evidence into a categorized changelog with user-facing impact.

Install in Claude Code

Use a Git checkout with a known previous release tag and the history for the target revision.

Get the complete `plugins/git/skills/generating-changelog` directory from the pinned GitHub checkout.
Copy it under the target project's `.claude/skills/`. Confirm `.claude/skills/generating-changelog/SKILL.md`, open Claude Code at the project root, and call `/generating-changelog`.

Example task

After `v1.2.0`, one change adds CSV export and another fixes export for an empty table. Draft the `v1.3.0` entries in Markdown before editing the changelog.

What to check

The draft describes CSV export under Added and the empty-table behavior under Fixed. It links those statements to the release range.

Original SKILL.md on GitHub · Updated 2026-11-13

Frequently asked question

Can a repo without Conventional Commits use the method?

Yes. Read the diffs or linked pull requests to classify changes that the commit subjects leave unclear.