Menu

Individual skill

to-release

0upvotes

Prepare a library release on its PR (version, changelog, draft GitHub release) for review, then tag and publish it after you merge.

skills/to-release/SKILL.md

Read pinned source

Source commit ced546848ec8eea8541e77b7aa041207b607462e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
20
Repository last updated
Oct 26, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# To Release

For libraries and other versioned packages. One command, two runs; the PR's state picks the phase: open → **prepare**, merged → **publish**. You review and merge in between. This skill never merges.

## 1. Resolve

`gh auth status` fails → stop: "Run `gh auth login`, then `/hb:to-release` again." PR from `$ARGUMENTS`, else the current branch's: `gh pr view <PR> --json number,state,headRefName,baseRefName,mergeCommit,title,body`. Closed unmerged → stop.

Versions follow [semver](https://semver.org): `MAJOR.MINOR.PATCH`, pre-releases `X.Y.Z-<id>.N` with `alpha` < `beta` < `rc` < the release. `git fetch origin --tags`, then sort with `git -c versionsort.suffix=- tag --sort=-v:refname`: plain `v:refname` ranks `1.0.0` below its own `-rc`. The first line is the previous tag; the first without a `-` suffix is the previous stable. New tags match their format (`v1.2.3` or `1.2.3`). No tag yet → first release at the manifest version.

## Prepare (PR open)

2. **Checks**: `gh pr checks <PR>` red or pending → stop and report.
3. **Version**: a manifest in the PR (`package.json`, `.claude-plugin/plugin.json`, `Cargo.toml`, `pyproject.toml`, …) is ahead of the previous tag → use it. Otherwise:
Back to top