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".From its SKILL.md
npx -y skills add tobihagemann/turbo --skill create-changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 3 commands, including `gh release list --limit 100 --json tagName,name,publishedAt,body` and 2 more.
SKILL.md
1.5 KB, 278 tokens by cl100k_base, 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,bodyto 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:refnameto list tags. For each consecutive tag pair, rungit log <older-tag>..<newer-tag> --onelineto 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).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.