Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-15 | ✗→✓ | ▲ Improved | -3% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -15% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -37% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -26% | 0% |
| case-06 | ✓→✓ | = Same ✓ | 50% | 0% |
A changelog is for users deciding whether to upgrade, not a commit dump. Format: Keep a Changelog + semver sections.
git describe --tags --abbrev=0.Collect commits since: git log <tag>..HEAD --oneline --no-merges.
Added (feat) · Fixed (fix) · Changed (behavior changes, perf)Deprecated · Removed · Securitychore/ci/test/docs noise unless user-visible.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.
only Fixed → patch (pre-1.0: breaking → minor).
CHANGELOG.md:markdown ## 0.2.0] - 2026-06-10 ### Added
engram watch picks up edits automatically.### Fixed
## [Unreleased] section at the very top for changes landing betweenreleases; 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.
Other measured skills in the registry, with their headline benchmark lift.