release is agent-read markdown (skill) from jebel-quant/rhiza-claude: Release any git repo that declares its version locations (no .rhiza/ needed) in one run — choose a version from a table, bump, regenerate the changelog, open a release PR, let the forge merge it once its checks pass, then tag the merged commit..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
You are running `/release` in the **current working directory's repo**. Goal: land the
version bump on the default branch **through a pull request**, like every other change,
and tag the commit that actually merged — in **one run**.
**A tag still cannot be cut before the merge, which is why there is a wait in the
middle.** A tag must point at a commit that exists on the branch you publish from; a
squash-merge replaces the branch's commits with a new one, so a tag created before the
merge names a SHA that never lands. No reordering of the steps fixes that — the commit to
tag does not exist until the request merges. So the run goes *through* the merge instead
of stopping in front of it: it hands the merge to the forge, waits for the bump to appear
on the default branch, and tags what landed.
| Stage | Steps | Ends with |
| --- | --- | --- |
| **Prepare** | 2–9 | the version chosen, the bump and changelog committed on a pushed branch, an open release PR |
| **Land** | 10–11 | auto-merge handed to the forge, and the bump on the default branch |
| **Tag** | 12–13 | the merged commit tagged, the tag pushed, release CI running |
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_h7st3oquictp7twp
GET https://markdownregistry.com/api/v1/resolve?ref=jebel-quant/rhiza-claude/release
GET https://markdownregistry.com/api/v1/blob/ea2040aee2fb6665344777c5ce7745e073154d7f84a209c1f2756a79ecab7f90
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jebel-quant/rhiza-claude · bundle/skills/rhiza-completions/SKILL.md · Install shell tab-completion for make targets, so `make <TAB>` lists a project's targets. Writes to the user's data…
jebel-quant/rhiza-claude · bundle/skills/rhiza-detach/SKILL.md · Detach this repo from rhiza — delete every rhiza-managed file listed in .rhiza/template.lock, prune the emptied…
jebel-quant/rhiza-claude · bundle/skills/rhiza-docs/SKILL.md · Create or refresh this repo's README.md, CLAUDE.md and mkdocs.yml, detecting project metadata from git and the…
jebel-quant/rhiza-claude · bundle/skills/rhiza-fix/SKILL.md · Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement…
jebel-quant/rhiza-claude · bundle/skills/rhiza-init/SKILL.md · Make the current folder a rhiza-managed repo — write the .rhiza/template.yml pointer, add a skeleton and license, open…
jebel-quant/rhiza-claude · bundle/skills/rhiza-maffay/SKILL.md · Print one bonmot from a random Peter Maffay song — a pick-me-up for a long refactor. Takes an optional theme keyword…
jebel-quant/rhiza-claude · bundle/skills/rhiza-quality/SKILL.md · Run the Rhiza code-quality gates and score this repo, then optionally file findings as issues. Falls back to a…
jebel-quant/rhiza-claude · bundle/skills/rhiza-release/SKILL.md · Release any git repo that declares its version locations (no .rhiza/ needed) in one run — choose a version from a…
jebel-quant/rhiza-claude · bundle/skills/rhiza-remote/SKILL.md · Check what CI on the origin says about this repo's open pull/merge requests, then diagnose and fix the red ones on…
jebel-quant/rhiza-claude · bundle/skills/rhiza-status/SKILL.md · Report this repo's rhiza state — whether the config is valid, and what was actually synced. Read-only. Add --files for…
jebel-quant/rhiza-claude · bundle/skills/rhiza-update/SKILL.md · Sync this rhiza-managed repo to the latest (or a given) template release and open a PR containing only template-owned…
yeachan-heo/oh-my-claudecode · skills/release/SKILL.md · Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
different-ai/openwork · .opencode/skills/release/SKILL.md · Cut an OpenWork release, release the app, publish a new version, rerun or recover a release tag, verify release assets…
blockrunai/clawrouter · skills/release/SKILL.md · Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm…
vellum-ai/vellum-assistant · .claude/skills/release/SKILL.md · Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.
arcee-ai/nac · .agents/skills/release/SKILL.md · Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks…
