A release workflow for preparing and publishing a software version. It can determine whether a release is stable or a release candidate, where a release candidate is a pre-release version for final testing.

Use it when bumping a version, creating stable or pre-release tags, making a GitHub release, or preparing an npm publication.

It gathers version checks, branch checks, tagging, pushing, GitHub release creation, and optional npm publishing into one process.

release — Skill for Claude Code by NikiforovAll

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 NikiforovAll/claude-code-marketplace --skill release

Clone the repo

git clone --depth 1 https://github.com/NikiforovAll/claude-code-marketplace

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/nikiforovall/claude-code-marketplace/release.svg)](https://agentmods.dev/skills/nikiforovall/claude-code-marketplace/release)

Your own site

<a href="https://agentmods.dev/skills/nikiforovall/claude-code-marketplace/release"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-marketplace/release.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 963 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.00060	$0.00963
Opus 5	$0.00030	$0.00481
Sonnet 5	$0.00012	$0.00193
Haiku 4.5	$0.00006	$0.00096

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

How it starts

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

Release

Bump version, tag, push, create a GitHub release with auto-generated notes, and present npm publish command. Supports both stable releases and release candidates (RC).

Inputs

$ARGUMENTS — target version (e.g. 1.15.0), rc for release candidate, or empty for auto-detection.

Release Type Detection

Determine release type from $ARGUMENTS and current branch:

If $ARGUMENTS contains rc, or current branch is not main/master → RC release
If $ARGUMENTS is a version like 1.15.0-rc.1 → RC release with that exact version
Otherwise → Stable release

Workflow

Step 1: Verify Clean Working Tree

Run git status --short. If there are uncommitted changes, warn the user and stop.

Step 2: Determine Branch & Release Type

git branch --show-current

Stable release: must be on main or master. If not, warn and ask to confirm or switch to RC.
RC release: can ship from any branch.

Step 3: Determine Version

Read current version from package.json. If $ARGUMENTS is an exact version, use it directly.

For stable releases:

Analyze commits since the last stable tag (exclude RC tags) to suggest a bump type:

major — breaking changes
minor — new features (feat commits)
patch — bug fixes, chores, docs only

Present the suggested bump type and resulting version to the user using AskUserQuestion with options: patch, minor, major (put the recommended one first with "(Recommended)" suffix).

For RC releases:

If current version is already an RC (e.g. 1.19.0-rc.1), auto-increment: 1.19.0-rc.2
If current version is stable (e.g. 1.18.0), determine the next minor/patch version and append -rc.1
Present the suggested RC version to the user using AskUserQuestion with options showing the auto-incremented version and a "next minor RC" / "next patch RC" alternative.

Step 4: Bump Version

Update version field in package.json to the target version.

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

8d ago First seen · 122 lines · 60 tokens per session scan A cbb02c5b4802

Subscribe to this mod's changes

release is a skill published in the GitHub repository NikiforovAll/claude-code-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 963 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 anthropic claude developer-tools marketplace plugins

changelog-summarizing

Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…

shopwareLabs/ai-coding-tools · 106 tokens

plugin-updating

Use this skill when the user asks to bump, update, or release a new version of a plugin in the Shopware AI Coding Tools marketplace — phrases like "bump test-writing to 3.8.0", "release a patch for dev-tooling", "update the plugin version". Handles synchronized version bumps across plugin.json and every SKILL.md…

shopwareLabs/ai-coding-tools · 102 tokens

release-info-writing

Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…

shopwareLabs/ai-coding-tools · 154 tokens

release