Create changelog

Skill tobihagemann/turbo/claude/skills/create-changelog

A composable dev process for agentic coding harnesses, packaged as modular skills. Turbo has sibling editions for Claude Code and Codex.

Install

npx -y skills add tobihagemann/turbo --skill create-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.5 KB, as published. Nobody here has run it

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