release SKILL.md skillB
release from jebel-quant/rhiza-claude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jebel-quant/rhiza-claude/release@git:20260907.b330822Pins git:20260907.b330822 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jebel-quant/rhiza-claude
- Path
plugin/skills/release/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260907.b330822, committed Sep 7, 2026
- First version recorded
- Aug 5, 2026
- Size
- 38,239 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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 | …
Read the whole file at its exact version.
How to install
mdr add jebel-quant/rhiza-claude/release@sha256:ea2040aee2fb6665The line at the top of this page pins the label git:20260907.b330822, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_h7st3oquictp7twp)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 5, 2026 and Sep 7, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260907.b330822 latest | 2026-09-07 | b330822 | 38,239 B | B | view · diff |
| git:20260907.ef3a538 | 2026-09-07 | ef3a538 | 29,008 B | B | view · diff |
| git:20260806.d392194 | 2026-08-06 | d392194 | 25,951 B | B | view · diff |
| git:20260806.23f5c51 | 2026-08-06 | 23f5c51 | 24,528 B | B | view · diff |
| git:20260805.5f28410 | 2026-08-05 | 5f28410 | 23,490 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (38239 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
jebel-quant/rhiza-claude · 6 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
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 AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from jebel-quant/rhiza-claude
Every file in jebel-quant/rhiza-claude