What is create-release?

A release workflow for publishing a versioned GitHub release with automatically generated notes. It uses semantic versioning, a convention such as v1.2.3 where each number describes the scale of change.

Use it to choose or calculate a version, review commits, create release notes, tag the code, and publish a GitHub release from the master branch.

It reduces manual work and helps prevent releases from being made from the wrong branch or with unclear version numbers. It also organizes changes since the previous release.

create-release — Skill by fpindej

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.

agentmods

npx agentmods add skills/fpindej/netrock/create-release

Any agent

npx skills add fpindej/netrock --skill create-release

Clone the repo

git clone --depth 1 https://github.com/fpindej/netrock

Made for: Claude Code, Codex.

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

When invoked 681 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	$0.00010	$0.00681
Opus 5	$0.00005	$0.00341
Sonnet 5	$0.00002	$0.00136
Haiku 4.5	$0.00001	$0.00068

Measured 2d ago against content hash 597842b2e79d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-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 2d 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/create-release/SKILL.md · 68 lines

How it starts

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

Creates a GitHub release with auto-generated release notes.

Hard rules

Only release from master. If not on master, switch first.
No Co-Authored-By lines in commits.
Tag signing follows the developer's git config (tag.gpgSign) - never pass -s/-S explicitly; fresh clones may have no signing key.
Releases use semantic versioning (vMAJOR.MINOR.PATCH).

Steps

Ensure you are on master and up to date: git checkout master && git pull
Determine the version:
- If the user provided a version (e.g., v1.2.3), use it
- If the user provided a bump type (major, minor, patch), calculate from the latest tag:
```
git tag --list 'v*' --sort=-v:refname | head -1
```
- If no argument and no tags exist, ask the user what version to use
- If no argument but tags exist, default to patch bump

Check what changed since the last release:

# If previous tag exists:
git log <previous-tag>..HEAD --oneline
# If first release:
git log --oneline -50

Generate release notes by categorizing merged PRs and commits since the last tag. Group changes into these categories (omit empty categories):
- New Features - feat: commits and feature PRs
- Security - security: or security-related changes
- Bug Fixes - fix: commits
- Improvements - refactor:, perf: commits
- Documentation - docs: commits
- Infrastructure - chore:, ci:, build: commits
Format each entry as: - Description (#PR) where possible.

Add a brief intro paragraph summarizing the release highlights before the categories.

Create the tag and release:

git tag -a <version> -m "Release <version>"
git push origin <version>
gh release create <version> --title "<version>" --notes "<release-notes>"

Report the release URL.

Version Bumping Reference

Given vMAJOR.MINOR.PATCH:

major - breaking changes or major milestones (v1.0.0 -> v2.0.0)
minor - new features, no breaking changes (v1.0.0 -> v1.1.0)
patch - bug fixes, docs, refactors (v1.0.0 -> v1.0.1)

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

2d ago First seen · 68 lines · 10 tokens per session scan A 597842b2e79d

Subscribe to this mod's changes

create-release is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 681 once invoked, about $0.0001 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.

Git and workflow Releases clean-architecture docker dotnet postgresql saas-template svelte

create-release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Hard rules

Steps

Version Bumping Reference

What this file has done since we first saw it

Other skills, from other repositories

prepare-release

finish-change

api-design

python

python-testing

react