Menu
Prepare the next release of DistroShelf: version bump, release notes, commit, and tag.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/ranfdev/DistroShelf --skill releaseThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | release |
| description | Prepare the next release of DistroShelf: version bump, release notes, commit, and tag. |
Your task is to prepare the next release for the DistroShelf project:
Analyze changes: Retrieve all commits since the last tag using git log --oneline --reverse $(git describe --tags --abbrev=0)..HEAD. Ensure you get the full list (not truncated).
Categorize changes: From commit messages, identify user-visible changes and classify them using the existing release note convention from data/com.ranfdev.DistroShelf.metainfo.xml.in:
New: — new featuresImproved: — enhancements to existing featuresFix: — bug fixesChanged: — behavior changes or removalsi18n: — translation updates (only note new languages)Ignore internal refactors, dependency bumps, documentation-only changes, and other non-user-facing changes.
Write release notes: Append the new release entry at the top of the <releases> section in data/com.ranfdev.DistroShelf.metainfo.xml.in. Use the existing format:
<release version="X.Y.Z" date="YYYY-MM-DD">
<description translate="no">
<ul>
<li>New: Feature description.</li>
<li>Fix: Bug description.</li>
</ul>
</description>
</release>
Determine version: Follow semver (major.minor.patch) based on the types of changes:
Update version: Bump the version: field in meson.build (line 2) to match.
Commit & Tag: Stage changes, commit with message vX.Y.Z, and create an annotated tag vX.Y.Z:
git add -A && git commit -m "vX.Y.Z"
git tag vX.Y.Z