Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/prepare-changelog
Guidelines for preparing changelog entries for nextest releases following Keep a Changelog format
Passed 23 of 25 test cases with the skill, and 12 of 25 without it.
and 15 more in the full report
11 fixed12 passed either way2 still failing0 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.
What exact `git` command should be run to list commit subjects oneline between previous tag `v0.9.0` and `main` when preparing a changelog?
| Checked | Without skill | With skill |
|---|---|---|
| Uses command "git log v0.9.0..main --oneline" | Missed | Passed |
The instructions your model reads when the skill loads.
This document describes the format and conventions used in site/src/changelog.md.
The changelog follows the Keep a Changelog format with nextest-specific conventions.
## [X.Y.Z] - YYYY-MM-DD
Sections should appear in this order (only include sections that are relevant):
### for section headers (e.g., ### Added)-test cases passed, vs 12 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.