A release helper for changing software versions, creating Git tags, and keeping version references consistent across project files. A Git tag is a named marker for a specific point in the code history.

Use it when making major, minor, or patch releases, updating versions in package and Docker files, tagging commits, and pushing a release tag.

It removes repetitive version edits and helps keep release files synchronized before the continuous-integration workflow runs.

release — Skill for Claude Code by madeinoz67

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 madeinoz67/madeinoz-knowledge-system --skill release

Clone the repo

git clone --depth 1 https://github.com/madeinoz67/madeinoz-knowledge-system

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/madeinoz67/madeinoz-knowledge-system/release/github.svg)](https://agentmods.dev/skills/madeinoz67/madeinoz-knowledge-system/release)

Your own site

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

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

When invoked 1,500 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.00057	$0.01500
Opus 5	$0.00028	$0.00750
Sonnet 5	$0.00011	$0.00300
Haiku 4.5	$0.00006	$0.00150

Measured 10d ago against content hash 78abd2d03cd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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 · 215 lines

How it starts

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

Release Automation Skill

Purpose

Automate the release process for the Madeinoz Knowledge System, including version synchronization across all files, git tagging, and triggering the CI workflow.

When to Use

Use this skill when:

Creating a new release (major, minor, or patch version)
Bumping the version number
Tagging a release commit
Pushing a release to trigger CI workflow
Synchronizing version numbers across multiple files

Version Sync Locations

The following files MUST be updated with the new version:

Primary Version Files

package.json (line 3)
```
"version": "X.Y.Z"
```
docker/Dockerfile (line 8)
```
LABEL version="X.Y.Z"
```

README.md (line 6)

pack-id: madeinoz67-madeinoz-knowledge-system-core-vX.Y.Z

src/skills/SKILL.md (line 3)
```
version: X.Y.Z
```

Production Docker Compose (Manual Update)

src/skills/server/docker-compose-production.yml (line 85)

image: ghcr.io/madeinoz67/madeinoz-knowledge-system:X.Y.Z

Note: All other docker-compose files use :latest tag and do NOT need updates.

Do NOT Edit

CHANGELOG.md - Auto-generated by git-cliff workflow
Modifying this file will conflict with automated changelog generation

Pre-Release Checklist

Before creating a release, verify:

# 1. Check you're on main branch
git branch --show-current  # Should output: main

# 2. Pull latest changes
git pull origin main

# 3. Verify working tree is clean (no uncommitted changes)
git status  # Should show: "nothing to commit, working tree clean"

# 4. Verify latest CI passed
gh run list --limit 1  # Check status is "completed success"

Release Workflow

Step 1: Update Version Numbers

Manually edit the version files listed above. For example, bumping from 1.8.0 to 1.9.0:

# Edit package.json
# Edit docker/Dockerfile
# Edit README.md
# Edit src/skills/SKILL.md
# Edit src/skills/server/docker-compose-production.yml

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

10d ago First seen · 215 lines · 57 tokens per session scan A 78abd2d03cd8

Subscribe to this mod's changes

release is a skill published in the GitHub repository madeinoz67/madeinoz-knowledge-system (3 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 1,500 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-31.

Claude Code Git and workflow Releases graphitti knowledge-graph pai personal-ai-infrastructure skill

clawhub-production-release

Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.

openclaw/clawhub · 62 tokens

devops/changelog-generation

A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.

echoVic/boss-skill · 36 tokens

github-release-notes-writer

Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…

flc1125/skills · 84 tokens

github-release-pr-writer

Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration…

flc1125/skills · 80 tokens

otel-changelog-pr-verifier

Verify whether CHANGELOG entries in an OpenTelemetry Go repository point to the correct pull requests and whether each (#NNNN) matches the described change. Use when checking a release PR, validating a CHANGELOG section, or screening only mismatched changelog-to-PR references.

flc1125/skills · 62 tokens

launch-and-growth

Get an open-source project in front of the people who need it, and keep them. Use when preparing to announce a project, writing a Hacker News or Reddit or Product Hunt post, planning a launch, writing a blog post about a release, improving GitHub discoverability (topics, About, social preview), or when the user asks…

the-open-agent/oss-skills · 108 tokens