Claude Skill

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

LLM Mart · 0 points · 24 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download tobihagemann-turbo-codex_skills_create-changelog-b903a85.zip · 0 KB

tobihagemann/turbo 403 31 forks MIT Updated 1d ago

Part of tobihagemann/turbo — 147 skills

Install

skills CLI npx skills add https://github.com/tobihagemann/turbo/tree/main/codex/skills/create-changelog

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tobihagemann-turbo@llmmart

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

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tobihagemann/turbo collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Create Changelog

Create a changelog backfilled with version history.

Step 1: Run `$changelog-rules` Skill

Run the $changelog-rules skill to load shared changelog conventions.

Step 2: Check for Existing Changelog

Use git rev-parse --show-toplevel to find the repository root. Look for the changelog file per $changelog-rules. If it already exists, use request_user_input to confirm overwriting it. If the user declines (chooses the free-form "Other" option or asks to abort), stop without running the remaining steps.

Step 3: 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 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).

Files (turbo)

SKILL.md 1.8 KB

---
name: create-changelog
description: "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\"."
---

# Create Changelog

Create a changelog backfilled with version history.

## Step 1: Run `$changelog-rules` Skill

Run the `$changelog-rules` skill to load shared changelog conventions.

## Step 2: Check for Existing Changelog

Use `git rev-parse --show-toplevel` to find the repository root. Look for the changelog file per `$changelog-rules`. If it already exists, use `request_user_input` to confirm overwriting it. If the user declines (chooses the free-form "Other" option or asks to abort), stop without running the remaining steps.

## Step 3: Backfill Version History

Collect release history from the most authoritative source available:

1. **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.
2. **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 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).