Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →silverstein/minutes-release-notes
Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks.
Passed 14 of 18 test cases with the skill, and 6 of 18 without it.
and 9 more in the full report
11 fixed7 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I fixed a bug in the Minutes audio capture daemon where buffer overflow occurred during high CPU load. Write a single conventional commit message summarizing this bug fix.
| Checked | Without skill | With skill |
|---|---|---|
| Provides a single-line fix format commit message | Missed | Passed |
The instructions your model reads when the skill loads.
Draft release notes that explain why a Minutes release matters without making users decode the commit history. Produce a draft only. Do not create, edit, or publish a GitHub release unless the user explicitly asks.
Collect:
v0.22.0HEADResolve missing refs from the repository instead of guessing:
git describe --tags --abbrev=0
git log <previous-tag>..HEAD --pretty='%s (%h)'
When HEAD is already tagged, resolve the previous tag from its parent so the range does not collapse to zero commits:
git describe --tags --abbrev=0 HEAD^
Confirm both refs with git rev-parse --verify before drafting. If the version or range is ambiguous, ask one short question.
Read two or three recent stable releases before writing:
gh release list --limit 5
gh release view <recent-tag>
test cases passed, vs 6 / 18 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.