release is agent-read markdown (skill) from pisberg/vibetags: 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..
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
# 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
…
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.
A 17 of 17 checks passed. Deterministic, no model, same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (15344 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
GitHub
pisberg/vibetags · 25 stars · license MIT · pushed 2026-09-25 · 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/bebe7a4dc37299ca77fe36727f3434e0df37c5e0f1195d0f237e0211b0ad9fed
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.
pisberg/vibetags · .claude/skills/add-annotation/SKILL.md · Add a new @AI... guardrail annotation to VibeTags — register it in GuardrailAnnotations, then wire it through every…
pisberg/vibetags · .claude/skills/add-platform/SKILL.md · Add support for a new AI coding tool, IDE, PR-reviewer, or context-packer to VibeTags — wire a new generated output…
pisberg/vibetags · .claude/skills/bump-dependencies/SKILL.md · Bump every third-party dependency, plugin and toolchain pin in VibeTags to its latest stable release, mirror the pins…
pisberg/vibetags · .claude/skills/consultation-loop/SKILL.md · Pre-push adversarial interrogation of the current branch's diff by a fresh reviewer with no memory of writing it - five…
pisberg/vibetags · .claude/skills/consumer-regression-suite/SKILL.md · Build every downstream consumer of VibeTags against a chosen VibeTags version and report which ones actually pass. Use…
pisberg/vibetags · .claude/skills/correctness-hunt/SKILL.md · Run a bug hunt against this repository under a fixed work order - baseline the suite, hunt with named bug-shape lenses…
pisberg/vibetags · .claude/skills/load-tests/SKILL.md · Run the VibeTags benchmark harness in load-tests/ and report the numbers honestly — annotation-volume and memory…
pisberg/vibetags · .claude/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…
pisberg/vibetags · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
pisberg/vibetags · .claude/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent…
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…
