release SKILL.md skillA
release from pisberg/vibetags is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pisberg/vibetags/release@git:20261023.06e494dPins git:20261023.06e494d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pisberg/vibetags
- Path
.claude/skills/release/SKILL.md- Versions recorded
- 14
- Latest version
- git:20261023.06e494d, committed Oct 23, 2026
- First version recorded
- Sep 10, 2026
- Size
- 17,970 bytes
- Repository stars
- 25
- License
- MIT
Cut a new VibeTags release — bump the version everywhere, update the CHANGELOG, open the release PR, and create the GitHub release that triggers Maven Central publishing. Use when the user says "release", "/release", "cut a release", "publish a new version", or asks to bump VibeTags to a new version.
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
# Release VibeTags Drives the release process documented in `docs/RELEASING.md`. That document is the source of truth; this skill is the executable path through it. If the two ever disagree, `docs/RELEASING.md` wins — and say so rather than silently improvising. ## Step 1 — Establish the current version and ask for the next one The single source of truth for "what version are we on" is the `<revision>` property in `vibetags-parent/pom.xml`: ```bash sed -n 's:.*<revision>\(.*\)</revision>.*:\1:p' vibetags-parent/pom.xml | head -n1 git tag --sort=-v:refname | head -5 ``` Then **ask the user which version to release** with `AskUserQuestion`. Compute the candidates from whatever the current version turns out to be — do not hardcode them: - If the current version is a release candidate (`X.Y.Z-RCn`), offer promoting it to final (`X.Y.Z`) and cutting the next candidate (`X.Y.Z-RC<n+1>`). - If the current version is final, offer the patch, minor, and major bumps, and a first release candidate for the next minor if that fits what is in `[Unreleased]`. Always include the semantic-versioning meaning in each option's description. The user …
Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/release@sha256:6f46cedfc45367b1The line at the top of this page pins the label git:20261023.06e494d, 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_golqe7qe3y4jf23u)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 14 versions of this file, between Sep 10, 2026 and Oct 23, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.06e494d latest | 2026-10-23 | 06e494d | 17,970 B | A | view · diff |
| git:20261009.aef590b | 2026-10-09 | aef590b | 18,303 B | A | view · diff |
| git:20261009.b325509 | 2026-10-09 | b325509 | 17,638 B | A | view · diff |
| git:20261009.5e6f4b9 | 2026-10-09 | 5e6f4b9 | 17,281 B | A | view · diff |
| git:20261008.7d1bd15 | 2026-10-08 | 7d1bd15 | 17,260 B | A | view · diff |
| git:20261008.7413a9a | 2026-10-08 | 7413a9a | 16,284 B | A | view · diff |
| git:20261006.495c058 | 2026-10-06 | 495c058 | 16,285 B | A | view · diff |
| git:20261006.2fd4794 | 2026-10-06 | 2fd4794 | 16,129 B | A | view · diff |
| git:20260925.634d539 | 2026-09-25 | 634d539 | 15,468 B | A | view · diff |
| git:20260922.9f95d19 | 2026-09-22 | 9f95d19 | 15,344 B | A | view · diff |
| git:20260921.72ea14c | 2026-09-21 | 72ea14c | 15,332 B | A | view · diff |
| git:20260919.0d98a54 | 2026-09-19 | 0d98a54 | 15,028 B | A | view · diff |
| git:20260912.34fb028 | 2026-09-12 | 34fb028 | 14,955 B | A | view · diff |
| git:20260910.a27bf9c | 2026-09-10 | a27bf9c | 14,155 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17970 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
Source
pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_golqe7qe3y4jf23u GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/release GET https://markdownregistry.com/api/v1/blob/6f46cedfc45367b1234febbff22d07e26a64086e511fe946e2dc8e5da514661b
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 pisberg/vibetags
Every file in pisberg/vibetags