A release helper for the pz Zig project. It chooses or applies a version increase, runs tests and cross-platform build checks, then commits, pushes, and tags the release.

Use it to publish a patch, minor, or major release, or to infer the version change from recent commits. It checks builds for Linux and macOS targets before pushing the release.

It groups the repetitive release checks and version-control steps into one procedure. Failed tests stop the release before the version is published.

How joelreymont/pz configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to joelreymont/pz. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/joelreymont/pz/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/joelreymont/pz

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joelreymont/pz/release.svg)](https://agentmods.dev/skills/joelreymont/pz/release)

Your own site

<a href="https://agentmods.dev/skills/joelreymont/pz/release"><img src="https://agentmods.dev/badge/skills/joelreymont/pz/release.svg" alt="Measured on agentmods" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 825 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.00825
Opus 5	$0.00032	$0.00413
Sonnet 5	$0.00013	$0.00165
Haiku 4.5	$0.00006	$0.00082

Measured 6d ago against content hash af5b908b89a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/release/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Skill for pz

Trigger Phrases

/release — auto-detect bump level from commits
/release patch or "bump patch" — patch bump (0.1.0 → 0.1.1)
/release minor or "bump minor" — minor bump (0.1.0 → 0.2.0)
/release major or "bump major" — major bump (0.1.0 → 1.0.0)

Procedure

1. Determine current version and bump level

Read build.zig.zon and extract current .version field.

Parse the argument (patch/minor/major). If no argument given, inspect commits since last tag to decide:

Any breaking change or "breaking" in message → major
New feature, "add", "feat" → minor
Everything else → patch

2. Compute new version

patch: X.Y.Z → X.Y.(Z+1)
minor: X.Y.Z → X.(Y+1).0
major: X.Y.Z → (X+1).0.0

3. Run tests

zig build test

If tests fail, stop and report.

4. Cross-compile check (don't overwrite native binary)

zig build check -Dtarget=x86_64-linux
zig build check -Dtarget=aarch64-linux
zig build check -Dtarget=aarch64-macos

5. Update version in build.zig.zon

Edit .version = "X.Y.Z" to new version. Use the Edit tool.

6. Commit and push

jj describe -m "Bump version to X.Y.Z"
jj git push

7. Tag and push tag

jj bookmarks conflict with git tags when they share names. Use git directly for tagging:

git tag vX.Y.Z $(jj log -r @ --no-graph -T 'commit_id' | head -c 40)
git push origin vX.Y.Z

8. Monitor release CI

gh run list --limit 1
gh run watch <run_id>

Wait for all 3 builds (x86_64-linux, aarch64-linux, aarch64-macos) and the release job to succeed.

9. Verify release

gh release view vX.Y.Z

Confirm 3 artifacts are attached:

pz-x86_64-linux.tar.gz
pz-aarch64-linux.tar.gz
pz-aarch64-macos.tar.gz

Report the release URL to the user.

10. If CI fails

# Delete the tag
git push origin :refs/tags/vX.Y.Z
git tag -d vX.Y.Z

Fix the issue, then restart from step 3.

Important

NEVER use zig build -Dtarget=... for cross-compile checks — it overwrites the native binary. Use zig build check -Dtarget=... instead.
The release workflow (.github/workflows/release.yml) triggers on v* tags and builds ReleaseFast binaries for 3 targets (x86_64-linux, aarch64-linux, aarch64-macos).
Version source of truth is build.zig.zon .version field, baked into the binary via build options.

Read the full file on GitHub · 111 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 111 lines · 64 tokens per session scan A af5b908b89a5

Subscribe to this mod's changes

release is a skill published in the GitHub repository joelreymont/pz (95 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 825 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud Git and workflow Releases

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).

garrytan/gstack · 35 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

agent-github-modes

Agent skill for github-modes - invoke with $agent-github-modes.

ruvnet/ruflo · 21 tokens

seed-snapshot-release

Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …

daangn/seed-design · 144 tokens

releasepr

Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.

compozy/compozy · 53 tokens

gitlab-devops

GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…

automateyournetwork/netclaw · 67 tokens

pz: Skill for Claude Code