What is release-prep?

A release checklist for Go projects that checks the repository state, reviews commits since the last version tag, suggests the next semantic version, and creates a test build.

Use it to prepare a release-readiness report, group changes for the changelog, propose a major, minor, or patch version, and run a snapshot build.

It gathers the information needed before a release and reduces mistakes in versioning or release notes. Publishing the release still requires manual approval.

release-prep — Skill for Claude Code by noah-hrbth/agent-tool-sync

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add noah-hrbth/agent-tool-sync --skill release-prep

Clone the repo

git clone --depth 1 https://github.com/noah-hrbth/agent-tool-sync

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/noah-hrbth/agent-tool-sync/release-prep/github.svg)](https://agentmods.dev/skills/noah-hrbth/agent-tool-sync/release-prep)

Your own site

<a href="https://agentmods.dev/skills/noah-hrbth/agent-tool-sync/release-prep"><img src="https://agentmods.dev/badge/skills/noah-hrbth/agent-tool-sync/release-prep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/noah-hrbth/agent-tool-sync/release-prep"><img src="https://agentmods.dev/badge/skills/noah-hrbth/agent-tool-sync/release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00063	$0.00861
Opus 5.5	$0.00025	$0.00344
Sonnet 5.5	$0.00013	$0.00172
Haiku 4.5	$0.00006	$0.00086

Measured 2mo ago against content hash e0563c3e25ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-prep 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 2mo 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.

.agentsync/skills/release-prep/SKILL.md · 105 lines

How it starts

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

Release Prep

Goal: produce a release-readiness report and a proposed version bump for the user to approve. Never tag, push, or invoke goreleaser release (non-snapshot) yourself — those actions affect remotes and are out of scope.

Procedure

1. Confirm clean state

git status --porcelain
git rev-parse --abbrev-ref HEAD

Abort with a clear message if there are uncommitted changes or the branch is not main. Releases should cut from a clean main.

2. Identify the current and previous tag

git describe --tags --abbrev=0    # latest tag, e.g. v0.4.2
git tag --sort=-v:refname | head -5

3. Summarize commits since the last tag

git log <last-tag>..HEAD --pretty=format:'%h %s'

Group the output by the changelog regex groups in .goreleaser.yaml (Features = ^.*feat[(\w)]*:+.*$, Bug fixes = ^.*fix[(\w)]*:+.*$, Refactors = ^.*refactor[(\w)]*:+.*$, Other = everything not excluded by ^docs:, ^chore:, ^test:, ^ci:, ^style:).

4. Propose the next version

Apply conventional-commit semver inference:

Any feat!: / BREAKING CHANGE: → bump major.
Any feat: (and no breaking) → bump minor.
Only fix: / refactor: / chore: → bump patch.
No commits since last tag → no release; report and stop.

State the proposed version and the rule that produced it.

5. Validate the goreleaser config

make release-check        # runs `goreleaser check`

Surface any errors verbatim.

6. Build a snapshot

make release-snapshot     # goreleaser release --snapshot --clean --skip=publish

This validates that the build pipeline (builds, archives, homebrew_casks rendering) succeeds locally without publishing. Then list dist/ and confirm the expected per-OS/per-arch archives are present:

ls dist/

7. Report

# Release prep: <proposed-version>

## Branch: main (clean)
## Last tag: <vX.Y.Z>
## Commits since: N

### Features
- <hash> <subject>

### Bug fixes
- <hash> <subject>

### Refactors
- <hash> <subject>

### Other
- <hash> <subject>

## Proposed version: <vX.Y.Z+1>
## Bump rule: <major | minor | patch> — <one-line justification>

## goreleaser check: <pass/fail>
## snapshot build: <pass/fail>
## dist artifacts: <count> archives

Read the full file on GitHub · 105 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.

2mo ago First seen · 105 lines · 63 tokens per session scan A e0563c3e25ab

Subscribe to this mod's changes

release-prep is a skill published in the GitHub repository noah-hrbth/agent-tool-sync (2 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 861 once invoked, about $0.0003 per session on Opus 5.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-31.

Git and workflow Releases

release-prep next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-prepnoah-hrbth/agent-tool-sync	Skill	2	2mo ago	MIT	A	63	Claude Code
release-announcementpaperclipai/paperclip	Skill	112k	today	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	today	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	9d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	today	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	789	2d ago	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	today	Apache-2.0	A	22	Claude Code, Codex