go-samples-gin-restful: Command for Claude Code

.claude/commands/pre-release.md

pre-release is a command for Claude Code from nanotaboada/go-samples-gin-restful. It costs 0 tokens per session (1,402 once invoked), scanned A, original, MIT.

A staged pre-release checklist that determines the next version and player codename from the repository history, then prepares the release. It pauses for approval before creating branches, commits, tags, or pushes.

In plain words
What is it for?
Use it to check the repository state, inspect version tags, choose the next codename, infer the version bump from CHANGELOG.md, and work through the release decisions.
Why use it?
It makes release preparation repeatable while keeping irreversible publishing actions under explicit human control.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is nanotaboada/go-samples-gin-restful's own configuration. It tells Claude Code how to work on go-samples-gin-restful itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything go-samples-gin-restful configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nanotaboada/go-samples-gin-restful. 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/nanotaboada/go-samples-gin-restful/master/.claude/commands/pre-release.md
Clone the repo
git clone --depth 1 https://github.com/nanotaboada/go-samples-gin-restful

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.

agentmods badge for pre-release

README.md
[![agentmods](https://agentmods.dev/badge/commands/nanotaboada/go-samples-gin-restful/pre-release.svg)](https://agentmods.dev/commands/nanotaboada/go-samples-gin-restful/pre-release)
Your own site
<a href="https://agentmods.dev/commands/nanotaboada/go-samples-gin-restful/pre-release"><img src="https://agentmods.dev/badge/commands/nanotaboada/go-samples-gin-restful/pre-release.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,402 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01402
Opus 5 $0.00000 $0.00701
Sonnet 5 $0.00000 $0.00280
Haiku 4.5 $0.00000 $0.00140

Measured 7d ago against content hash 9effcf1ee493, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pre-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 7d 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/commands/pre-release.md · 126 lines

How it starts

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

Run the pre-release checklist for this project. Work through all three phases in order, pausing for explicit confirmation at each decision point before proceeding. Never create a branch, commit, tag, or push without approval.


Phase 1 — Determine next release

  1. Run git status and confirm the working tree is clean and on master. If not, stop and report the problem.

  2. Run git tag --sort=-v:refname to list existing tags. Identify the most recent tag matching v*.*.*-* and extract its player codename.

  3. Read the A–Z player table from CHANGELOG.md to find the next player:

    • No tags yet: start at A (first player in the table).
    • Normal case: use the player that follows the last used codename alphabetically. If letters were skipped, pick the next after the highest existing codename — do not backfill gaps.
    • Last codename is Z (Zico): the list is finite. Stop and flag that the naming convention needs to be revisited before proceeding.
  4. Read the [Unreleased] section of CHANGELOG.md and infer the version bump using these rules (applied in order — first match wins):

    • Any entry contains the word BREAKING (case-insensitive), a BREAKING CHANGE: token in a commit footer, or a ! suffix after the commit type/scope (e.g. feat!: or feat(scope)!:) → major bump
    • Any ### Added entry introduces a new endpoint, request parameter, or client-visible API responseminor bump. Test additions, documentation (ADRs, README, Swagger regen), and internal tooling do not qualify.
    • Otherwise (only ### Changed, ### Fixed, ### Removed, or non-API additions) → patch bump
  5. Compute the next version by applying the bump to the current latest tag's semver (e.g. v2.0.0-bobby + minor → 2.1.0).

  6. Present a summary for confirmation before continuing:

    • Last tag and player
    • Next version and player codename
    • Bump type and the reasoning (what triggered it)
    • Proposed tag: vX.Y.Z-{player}
    • Proposed branch: release/vX.Y.Z-{player}

    Wait for explicit approval before proceeding to Phase 2.


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

  1. 7d ago First seen · 126 lines · 0 tokens per session scan A 9effcf1ee493

Subscribe to this mod's changes

pre-release is a command published in the GitHub repository nanotaboada/go-samples-gin-restful (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,402 tokens. 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.