Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ecnu-icalk/changelog-generator
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language.
Passed 17 of 20 test cases with the skill, and 12 of 20 without it.
and 4 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Convert this commit message into a user-facing release note entry: "fix(checkout): resolve payment gateway timeout during high load".
| Checked | Without skill | With skill |
|---|---|---|
| The entry strips the (checkout) scope tag. | Missed | Passed |
| The entry begins with the present tense verb Fix. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate structured, user-facing changelogs from git commit history.
Determine the commit range from the user's request, then fetch commits:
# Between tags/versions
git log v1.2.0..v1.3.0 --oneline --no-merges
# Since a date
git log --since="2024-03-01" --oneline --no-merges
# Since last tag (default when no range given)
git log "$(git describe --tags --abbrev=0)"..HEAD --oneline --no-merges
If there are no tags and no range specified, ask the user for a date or count.
Apply these rules based on the commit message prefix:
| Prefix / pattern | Category |
|---|---|
feat: feature: | New Features |
fix: bugfix: | Bug Fixes |
perf: | Performance |
BREAKING CHANGE or !: suffix | Breaking Changes |
security: vuln: | Security |
docs: test: ci: chore: refactor: style: build: | Skip (internal) |
For non-conventional messages, infer category from content. Exclude purely internal commits (test infra, CI config, linting, dependency bumps with no user impact).
Transform each kept commit into a clear, benefit-focused sentence:
test cases passed, vs 12 / 20 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.