ss-release

ss-release is a skill for Claude Code from MartyBonacci/specswarm. It costs 25 tokens per session (428 once invoked), scanned A, original, MIT.

A release-preparation workflow for creating a software version, including a changelog, version change, and Git tag. It asks for confirmation before proceeding.

In plain words
What is it for?
Use it to prepare patch, minor, or major releases, update the version, create release notes, and tag the code in Git.
Why use it?
It helps avoid incomplete or accidental releases by identifying the release type and confirming the action first.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the ss plugin — 10 skills, 34 commands, 6 agents, 4 hooks shipped together

Good fit Use it to prepare patch, minor, or major releases, update the version, create release notes, and tag the code in Git.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/martybonacci/specswarm/ss-release
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 MartyBonacci/specswarm --skill ss-release
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm

Made for: Claude Code.

Or install ss, the plugin that ships this one along with the rest of its 10 skills, 34 commands, 6 agents, 4 hooks.

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 ss-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/martybonacci/specswarm/ss-release.svg)](https://agentmods.dev/skills/martybonacci/specswarm/ss-release)
Your own site
<a href="https://agentmods.dev/skills/martybonacci/specswarm/ss-release"><img src="https://agentmods.dev/badge/skills/martybonacci/specswarm/ss-release.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 428 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.00025 $0.00428
Opus 5 $0.00013 $0.00214
Sonnet 5 $0.00005 $0.00086
Haiku 4.5 $0.00003 $0.00043

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

Security

Grade A, and why

ss-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.

plugins/ss/skills/ss-release/SKILL.md · 54 lines

What it actually says

SpecSwarm Release

Provides natural language access to /ss:release command.

When to Invoke

Trigger this skill when the user mentions:

  • Releasing a version
  • Cutting a release
  • Tagging and publishing
  • Version bumping
  • Creating a changelog

Examples:

  • "Release version 2.0"
  • "Cut a patch release"
  • "Tag and publish"
  • "Bump the minor version"
  • "Prepare a release"

Instructions

Confirm and extract version type:

  1. Detect that user wants to create a release

  2. Extract version type from context:

    • "patch" / "bug fix release" → --patch
    • "minor" / "new features" → --minor
    • "major" / "breaking changes" → --major
  3. If version type is clear, ask for confirmation using AskUserQuestion:

    Question: "Release Confirmation" Description: "This will run quality gates, generate changelog, bump version, and create a git tag." Options:

    • Option 1 (label: "Yes, create release"): "Run release workflow"
    • Option 2 (label: "No, cancel"): "Cancel release"
  4. If version type is unclear, ask which type:

    • Use AskUserQuestion with options: "Patch (bug fixes)", "Minor (new features)", "Major (breaking changes)", "Cancel"
  5. Execute: Run /ss:release --patch|--minor|--major based on selection

Semantic Understanding

Release equivalents: release, tag, publish, cut, version, bump, changelog Version terms: patch, minor, major, breaking, semver

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 · 54 lines · 25 tokens per session scan A 6193efb90705

Subscribe to this mod's changes

ss-release is a skill published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 428 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.