How do I install the Release skill?

Run npx skillmds@latest add tomevault-io/release-61 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by tomevault-io — Agent Skill

Name: Release
Author: tomevault-io

Release

Create a new GitLabBar release with proper versioning, git tag, and GitHub release. Use when the user asks to release, publish, ship, or create a new version of the app. Handles version bump in package.json, git commit, tag, push, and GitHub release creation with English release notes. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Release Process for GitLabBar

Input

The user may provide a version number (e.g. 0.3.0). If not provided, read the current version from package.json, increment the patch number, and ask the user to confirm the new version.

Steps

Read current version from package.json.
Determine new version: use the user-provided version or auto-increment patch. Validate it follows semver (MAJOR.MINOR.PATCH).
Check git status: ensure the working tree is clean or that all changes are committed. If there are uncommitted changes, ask the user whether to commit them first.
Bump version: update the version field in package.json to the new version.
Commit: stage package.json and commit with message Bump version to <version>.
Tag: create git tag v<version>.
Push: run git push origin main --tags to push commit and tag.
Wait for CI: the GitHub Actions workflow triggers on v* tags, builds the app, and creates the release with DMG and ZIP assets. Poll the workflow status with gh run list every 15 seconds until the run for the tag completes. Report success or failure.
Update release notes: once CI creates the release, update the body with gh release edit v<version> --notes "...". Generate notes by comparing commits since the previous tag:
- Use git tag --sort=-version:refname to find the previous tag
- Use git log --oneline <prev-tag>..v<version> to list changes
- Categorize into "What's New" (features, improvements) and "Fixes" (bug fixes)
- All notes must be written in English
- Follow this format:

## What's New

- **Feature name**: Short description.

## Fixes

- Short description of fix.

Verify: run gh release view v<version> and confirm:
- Release exists with correct tag
- Assets are attached with filenames containing the correct version number
- Release notes are present and in English
Report: display the release URL to the user.

Rules

All release notes and commit messages must be in English.
Never skip the version bump in package.json — build artifacts use this version in their filenames.
Always wait for CI to finish before updating release notes.
If CI fails, report the error and do not update notes.
Do not force-push or amend existing commits.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: release-61description: Create a new GitLabBar release with proper versioning, git tag, and GitHub release. Use when the user asks to release, publish, ship, or create a new version of the app. Handles version bump in package.json, git commit, tag, push, and GitHub release creation with English release notes. Use when this capability is needed.---# Release Process for GitLabBar## InputThe user may provide a version number (e.g. `0.3.0`). If not provided, read the current version from `package.json`, increment the patch number, and ask the user to confirm the new version.## Steps1. **Read current version** from `package.json`.2. **Determine new version**: use the user-provided version or auto-increment patch. Validate it follows semver (MAJOR.MINOR.PATCH).3. **Check git status**: ensure the working tree is clean or that all changes are committed. If there are uncommitted changes, ask the user whether to commit them first.4. **Bump version**: update the `version` field in `package.json` to the new version.5. **Commit**: stage `package.json` and commit with message `Bump version to <version>`.6. **Tag**: create git tag `v<version>`.7. **Push**: run `git push origin main --tags` to push commit and tag.8. **Wait for CI**: the GitHub Actions workflow triggers on `v*` tags, builds the app, and creates the release with DMG and ZIP assets. Poll the workflow status with `gh run list` every 15 seconds until the run for the tag completes. Report success or failure.9. **Update release notes**: once CI creates the release, update the body with `gh release edit v<version> --notes "..."`. Generate notes by comparing commits since the previous tag: - Use `git tag --sort=-version:refname` to find the previous tag - Use `git log --oneline <prev-tag>..v<version>` to list changes - Categorize into "What's New" (features, improvements) and "Fixes" (bug fixes) - All notes must be written in **English** - Follow this format:```## What's New- **Feature name**: Short description.## Fixes- Short description of fix.```10. **Verify**: run `gh release view v<version>` and confirm: - Release exists with correct tag - Assets are attached with filenames containing the correct version number - Release notes are present and in English11. **Report**: display the release URL to the user.## Rules- All release notes and commit messages must be in **English**.- Never skip the version bump in `package.json` — build artifacts use this version in their filenames.- Always wait for CI to finish before updating release notes.- If CI fails, report the error and do not update notes.- Do not force-push or amend existing commits.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/yoanbernabeu) — claim your Tome and manage your conversions.

Frequently asked questions