Install any skill in seconds. Free to start, no credit card required.
Get Started Free →omnigent-ai/changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type.
Passed 8 of 16 test cases with the skill, and 5 of 16 without it.
and 2 more in the full report
5 fixed6 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
What shell command gathers non-merge commit hashes and subjects for tag range v1.0.0..v1.1.0?
| Checked | Without skill | With skill |
|---|---|---|
| Executes git log with --no-merges and --pretty=format:'%h %s'. | Missed | Passed |
The instructions your model reads when the skill loads.
Turn a range of history into a clear changelog entry that a user can read to decide whether and how to upgrade.
Establish the range first. Honor an explicit one ("since v1.2.0", "the last 10
commits", "PRs merged this week"); otherwise default to commits since the most
recent tag (git describe --tags --abbrev=0 then git log <tag>..HEAD).
Collect the raw material yourself with sys_os_shell:
git log <range> --no-merges --pretty=format:'%h %s' for the commit subjects.git log <range> --merges or gh pr list --search "merged:>=<date>" for PRs.git diff <range> --stat to see the surface area, and gh pr view <n> for a
PR's intent when a subject line is terse.When a subject is unclear about user impact, dispatch the researcher
(purpose: explore) to read the diff and report what actually changed for
users — do not guess from the subject alone.
Use the Keep a Changelog categories, dropping any that are empty:
## <version or range> — <YYYY-MM-DD>
### Added
### Changed
### Deprecated
### Removed
### Fixed
### Security
test cases passed, vs 5 / 16 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.