- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill create-changelog -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill create-changelog -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill create-changelog -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill create-changelog -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/create-changelogFrom the publisher
Create a changelog backfilled with version history.
/changelog-rules SkillRun the /changelog-rules skill to load shared changelog conventions.
Use git rev-parse --show-toplevel to find the repository root. Look for the changelog file per /changelog-rules. If it already exists, use AskUserQuestion to confirm overwriting it. If the user declines (chooses the free-form "Other" option or asks to abort), stop without running the remaining steps.
Collect release history from the most authoritative source available:
gh release list --limit 100 --json tagName,name,publishedAt to list releases. For each release, read its notes with gh release view <tag> --json body --jq .body and parse them into changelog entries.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.
Write the changelog following the /changelog-rules file structure and conventions.
Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags).
Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"set up changelog\", or \"backfill changelog\"
---name: create-changelogdescription: Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to…---# claude/skills/create-changelog/SKILL.mdOverview
Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"set up changelog\", or \"backfill changelog\".
FAQ
Download claude/skills/create-changelog/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/tobihagemann/turbo.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.