Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →umputun/new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.
Passed 15 of 19 test cases with the skill, and 11 of 19 without it.
and 2 more in the full report
4 fixed13 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are calling the GitLab CLI glab tool to publish release notes for version v2.1.0. What flag names specify the release name and release notes body?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the --name flag to specify the release title in glab release create. | Passed | Passed |
| Uses the --notes flag to specify the release notes body in glab release create. | Missed | Passed |
The instructions your model reads when the skill loads.
Creates GitHub, GitLab, or Gitea releases with auto-versioning and release notes generation.
Helper scripts in skill's scripts/ directory (use ${CLAUDE_PLUGIN_ROOT} for path resolution):
detect-platform.sh - outputs github, gitlab, or giteacalc-version.sh <type> - outputs new version (e.g., v1.2.3)get-notes.sh <platform> - outputs release notes (PRs/MRs or commits)Every helper exits non-zero and prints the reason on stderr. If any of Steps 2, 5 or 6
fails, report that text to the user and abort the workflow - do not continue with an
empty value. get-notes.sh in particular fails when the forge CLI is missing,
unauthenticated or rate-limited; continuing there publishes a release whose notes list
none of its PRs.
On Gitea, get-notes.sh collects no PRs and returns commit-derived notes with a warning
on stderr, because tea pr list exposes neither a merged flag nor a merge timestamp. That warning
is not a failure - show it to the user with the preview in Step 8 and carry on.
Use AskUserQuestion tool to get release type:
{
"questions": [{
"question": "What type of release is this?",
"header": "Version",
"options": [
{"label": "Hotfix", "description": "Bug fixes (1.2.3 → 1.2.4)"},
test cases passed, vs 11 / 19 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.