Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags.
Passed 9 of 17 test cases with the skill, and 7 of 17 without it.
3 fixed9 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
When starting the workflow to generate a project changelog from historical data, what is the very first step that must be performed before running any file checks or git commands?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes the $changelog-rules skill to load conventions | Missed | Passed |
The instructions your model reads when the skill loads.
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 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.
Collect release history from the most authoritative source available:
gh release list --limit 100 --json tagName,name,publishedAt,body to get release notes. For each release, parse the body 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).
test cases passed, vs 7 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.