mcpbeat

Create Changelog

tobihagemann/turbo-create-changelog

Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"initialize changelog\", \"start a changelog\", \"set up changelog\", \"generate changelog\", or \"backfill changelog\".

391 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
398
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/tobihagemann/turbo --skill create-changelog

The instruction itself

6 sections, as written by the author

Create Changelog

Create a changelog backfilled with version history.

Step 1: Run $changelog-rules Skill

Run $changelog-rules to load shared changelog conventions.

Step 2: Backfill Version History

Collect release history from the most authoritative source available:

  • GitHub releases (preferred): Run gh release list --limit 100 --json tagName,name,publishedAt,body to get release notes. For each release, parse the body into changelog entries.
  • Git tags (fallback): If no GitHub releases exist, run git tag --sort=-v:refname to list tags. For each consecutive tag pair, run git log <older-tag>..<newer-tag> --oneline to collect commit summaries.

For each version, classify entries into the standard change types and apply the changelog-worthiness criteria per $changelog-rules.

Step 3: Check for Existing Changelog

If the changelog file already exists, warn the user and confirm before overwriting.

Step 4: Write Changelog

Write the changelog following the $changelog-rules file structure and conventions.

Step 5: Present the Result

Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags).

How to use it

Copy the folder

Take tobihagemann/turbo-create-changelog from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.