Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/release-notes
Draft user-facing release notes from a git log range.
Passed 19 of 22 test cases with the skill, and 16 of 22 without it.
and 2 more in the full report
3 fixed16 passed either way3 still failing0 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.
Please summarize what shipped between v1.4.2..HEAD for our end users. Organize the commits by their impact—especially highlighting any breaking changes or fixes—and rewrite internal messages into clean user-accessible bullet points.
| Checked | Without skill | With skill |
|---|---|---|
| The recommended git log command uses tab-separated fields via `%x09`. | Missed | Passed |
| The recommended git log command includes the `--no-merges` flag. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate clear, user-facing release notes from git log between two refs.
v1.2.0..HEAD, last-tag..main)<latest tag>..HEAD if user didn't specify)git log <from>..<to> --pretty=format:'%h%x09%s%x09%an' --no-mergesfeat: / add: → Featuresfix: / bugfix: → FixesBREAKING CHANGE: (in body) → Breaking (top of doc, explicit migration note)chore:, docs:, refactor:, test:) → omit unless user-visiblefeat(api): prefix; no internal jargon)(#1234)), link it## <version> — <date>
### ⚠️ Breaking changes
- <one-sentence summary>. **Migration:** <what to do>. ([#PR])
### ✨ Features
- <user-visible benefit>. ([#PR])
### 🐛 Fixes
- <symptom that's now fixed>. ([#PR])
test cases passed, vs 16 / 22 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.