A release procedure for publishing a new version of structcli, a command-line software library.

Use it when preparing a release, including checking changes since the last version, identifying breaking changes, updating release notes, and creating the new tag.

It guides the version choice, changelog, checks, commit, push, and tag steps so releases follow a repeatable process.

How leodido/structcli configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to leodido/structcli. 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/leodido/structcli/main/.skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/leodido/structcli

Made for: Claude Code, Codex.

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/leodido/structcli/release/github.svg)](https://agentmods.dev/skills/leodido/structcli/release)

Your own site

<a href="https://agentmods.dev/skills/leodido/structcli/release"><img src="https://agentmods.dev/badge/skills/leodido/structcli/release/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/leodido/structcli/release"><img src="https://agentmods.dev/badge/skills/leodido/structcli/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 817 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.00054	$0.00817
Opus 5.5	$0.00022	$0.00327
Sonnet 5.5	$0.00011	$0.00163
Haiku 4.5	$0.00005	$0.00082

Measured 2mo ago against content hash d200167e2e7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.skills/release/SKILL.md · 62 lines

How it starts

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

Release structcli

Prerequisites

You are on main with a clean working tree.
Verify you can push to origin main (check git config user.email against GitHub email privacy settings if pushes are rejected).
All CI workflows (testing, wasm) are green on main.

Steps

1. Determine the version

Identify the next version from git tag --sort=-v:refname | head -1 and the nature of changes since the last tag (git log <last-tag>..HEAD --oneline). Look for feat!: or refactor!: prefixes indicating breaking changes.

2. Write the changelog

Gather merged PRs since the last tag. Each commit on main corresponds to a rebase-merged PR. Use the GitHub API to read PR titles, bodies, and labels.

Write the [Unreleased] section in CHANGELOG.md following Keep a Changelog format with these subsections as needed: Added, Changed, Removed, Fixed. Prefix breaking items in Changed with **Breaking:**.

Then:

Rename [Unreleased] to [X.Y.Z] - YYYY-MM-DD
Add a new empty [Unreleased] section above it
Update comparison links at the bottom of the file
Commit directly to main: git commit -m "docs(changelog): add vX.Y.Z release notes"
Push to main

3. Check for pending release process improvements

If there are Makefile or CI changes needed for the release process itself, open a PR with a chore: prefix (excluded from release notes by .github/release.yml). Wait for merge before proceeding.

4. Release

git checkout main && git pull origin main
make release VERSION=X.Y.Z

The Makefile target:

Guards: clean tree, on main
Bumps const Version in version.go
Regenerates examples/full/ (SKILL.md, llms.txt, AGENTS.md via go generate)
Bumps github.com/leodido/structcli version in all example go.mod files
Commits, tags vX.Y.Z, pushes main + tag

5. Verify

All three must pass:

releasing CI workflow — triggered by the tag push. Runs version-check (verifies version.go matches tag) then goreleaser (creates GitHub Release with auto-generated notes from PR labels).
GitHub Release — exists at https://github.com/leodido/structcli/releases/tag/vX.Y.Z. Auto-generated notes categorize PRs by label: breaking-change → "Breaking Changes", enhancement → "Features & Enhancements", bug → "Bug Fixes", documentation → "Documentation". The chore label is excluded.
Go module proxy — go list -m github.com/leodido/[email protected] resolves. May take a few minutes.

Read the full file on GitHub · 62 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 · 62 lines · 54 tokens per session scan A d200167e2e7c

Subscribe to this mod's changes

release is a skill published in the GitHub repository leodido/structcli (18 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 817 once invoked, about $0.0002 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-30.

Git and workflow Releases cli cobra configuration-files environment-variables flags viper

release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseleodido/structcli	Skill	18	3mo ago	MIT	A	54	Claude Code, Codex
rea-changelog-updatemorluto/rea	Skill	435k	yesterday	MIT	A	33	Claude Code
codew-release-qa-sweepHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	31	Claude Code, Codex
releaseHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	0	Claude Code, Codex
skillshare-releaserunkids/skillshare	Skill	2.9k	yesterday	MIT	A	77	Claude Code
skillshare-changelogrunkids/skillshare	Skill	2.9k	yesterday	MIT	A	134	Claude Code
githubAtomicBot-ai/atomic-agent	Skill	3.4k	8d ago	MIT	A	48	Claude Code, Codex

structcli: Skill for Claude Code