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\".

install

source · Clone the upstream repo

git clone https://github.com/tobihagemann/turbo

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/tobihagemann/turbo "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/create-changelog" ~/.claude/skills/tobihagemann-turbo-create-changelog && rm -rf "$T"

manifest: skills/create-changelog/SKILL.md

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).