Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/writing-modpack-changelog
Use when cutting a modpack release. Creates <project>/docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
Passed 16 of 21 test cases with the skill, and 9 of 21 without it.
and 10 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create a changelog entry for v1.4.0 with: fixed crash on exit, added HD textures, removed old ENB helper, updated weather compatibility notes, adjusted player movement speed. Use standard semantic bucket titles.
| Checked | Without skill | With skill |
|---|---|---|
| Uses exact standard category titles: Added, Changed, Fixed, Removed, Compatibility | Missed | Passed |
The instructions your model reads when the skill loads.
The modpack release changelog is the user-visible record of what changed between releases, grouped by semantic category: Added, Changed, Fixed, Removed, and Compatibility. This skill replaces the deleted templates/modpack/release-changelog.md template by creating <project>/docs/release-changelog.md at runtime, then inserting a new version section whenever the curator cuts a release.
| Use this skill when... | Result |
|---|---|
| The user says "cut a release", "release notes", "changelog", or "what changed since last version" | Create or update the release changelog. |
| A target version is being prepared for Nexus, ModDB, a Discord post, a GitHub release, or another player-facing surface | Produce grouped, readable release notes. |
| The user wants changes since the last tag, version, or release section | Summarize those changes into semantic buckets. |
| The user has finished a modpack milestone | Insert a new version section newest-first. |
| The user asks whether the release is major, minor, or patch | Suggest a version bump based on modpack impact. |
| Do not use this skill when... | Use instead |
|---|---|
| The user made a random working change and wants to remember it later | writing-modpack-devlog |
| The user wants a single-mod curator note | writing-modpack-devlog |
| The user asks for plugin inspection or conflict resolution | xedit-automation or xedit-conflict-audit first. |
| There is no release boundary, version, tag, or player-facing summary intent | Keep working; do not invent a release. |
| The user needs to set up the modpack project structure first | setting-up-bgs-modding-environment |
<modpack_project_root>, use it.Data/, profiles/, or docs/, default to pwd and tell the user what default you used.<project>/docs/release-changelog.md.
<project>/docs/ does not exist, create it.release-changelog.md is missing, create it before inserting the version.# <Project Name> Release ChangelogPlayer-facing release notes for <Project Name>. Newest releases are listed first.test cases passed, vs 9 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.