Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/changelog
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
1 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I wrote a multi-paragraph entry explaining the architectural re-design of our caching layer for the changelog. How should this entry be formatted?
| Checked | Without skill | With skill |
|---|---|---|
| The response limits the changelog entry to a single line. | Missed | Passed |
The instructions your model reads when the skill loads.
A changelog is for users deciding whether to upgrade, not a commit dump. Format: Keep a Changelog + semver sections.
Find the range. Last release tag: git describe --tags --abbrev=0.
Collect commits since: git log <tag>..HEAD --oneline --no-merges.
Bucket each commit:
Added (feat) · Fixed (fix) · Changed (behavior changes, perf)Deprecated · Removed · Securitychore/ci/test/docs noise unless user-visible.Rewrite each line user-first. Translate implementation into impact:
fix(ingest): treat mtime regressions as editsFixed duplicate chunks after restoring files from backup.
One line each; link the PR/issue number when the repo uses them.Squash threads. Five commits iterating on one feature = one entry.
Pick the version bump from the buckets: breaking → major, Added → minor, only Fixed → patch (pre-1.0: breaking → minor).
Write the section at the top of CHANGELOG.md:
## [0.2.0] - 2026-06-10
### Added
- Live re-indexing: `engram watch` picks up edits automatically.
### Fixed
- Duplicate chunks after restoring files from backup.
Keep an ## [Unreleased] section at the very top for changes landing between
releases; releasing = renaming it and starting a fresh one.
Every entry answers: what can I do now / what stopped being broken? If an entry needs the source code to make sense, rewrite it.
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.