Release

Automates the entire release workflow: validates your changelog, commits outstanding work, bumps versions, cuts tags, and pushes with CI monitoring. It enforces a strict Keep a Changelog format with prose highlights for major releases and detailed sections for changes and fixes. The pre-push hook blocks tag pushes unless package.json, CHANGELOG.md, and CI all align. It also checks for dependency updates to sqlite-vec and node-llama-cpp before cutting releases. The seven-step process is thorough but rigid: if you like automation that refuses to skip validation or force-push, this handles everything from `/release patch` to watching the publish workflow complete. Best for projects where changelog discipline matters more than speed.

skills.sh installs: 2.2K
GitHub stars: 31K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tobi/qmd --skill release --agent claude-code

Installs into .claude/skills of the current project.

Files

Release

Cut a release, validate the changelog, and ensure git hooks are installed.

Usage

/release 1.0.5 or /release patch (bumps patch from current version).

Process

When the user triggers /release <version>:

Gather context — run skills/release/scripts/release-context.sh <version>. This silently installs git hooks and prints everything needed: version info, working directory status, commits since last release, files changed, current [Unreleased] content, and the previous release entry for style reference.
Commit outstanding work — if the context shows staged, modified, or untracked files that belong in this release, commit them first. Use the /commit skill or make well-formed commits directly.
Write the changelog — if [Unreleased] is empty, write it now using the commits and file changes from the context output. Follow the changelog standard below. Re-run the context script after committing if needed.