A skill for managing a Git-based path from short-lived branches to the main branch, production, and an exact version tag.

Use it to follow the project's branch rules, promote changes to production, create releases, and handle production fixes.

It separates ordinary code integration from the stronger decision to release software, reducing mistakes such as tagging the wrong commit or promoting only part of the code.

release — Skill by ymm-oss

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/ymm-oss/fsl/release

Any agent

npx skills add ymm-oss/fsl --skill release

Clone the repo

git clone --depth 1 https://github.com/ymm-oss/fsl

Made for: Claude Code, Codex.

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

When invoked 3,816 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.00058	$0.03816
Opus 5	$0.00029	$0.01908
Sonnet 5	$0.00012	$0.00763
Haiku 4.5	$0.00006	$0.00382

Measured 2d ago against content hash f5a5fae1a66f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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/release/SKILL.md · 298 lines

How it starts

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

Operate the release flow

Treat CI-green pull requests as integration evidence and release promotion as a separate, stronger decision:

short-lived branch -> main -> production -> vX.Y.Z
                         ^          ^
                  integration   release readiness

Keep main as the default branch. Do not create develop or pre-production. Use a temporary release/vX.Y branch only when main must advance while an exact candidate is stabilized.

Read docs/RELEASE.md completely before promote or cut; it is the authoritative command-level procedure. Keep it and this lifecycle contract aligned in the same pull request.

Non-negotiable rules

Merge product and quality changes into main through pull requests.
Accept changes into production only through a release-promotion pull request.
Never tag main; tag the exact production commit approved for release.
Never selectively promote commits from main. Promote its complete tree.
Never force-move or reuse a published tag.
Publish only the tag-driven GitHub Release. Do not publish the frozen Python compatibility reference to PyPI or the Rust crates to crates.io.
Release native binaries for macOS arm64, Linux x64, Linux arm64, and Windows x64 only. Intel macOS (macos-x64) is not supported.
Populate the GitHub Release body from the matching non-empty changelog section.
Fix defects upstream in main first, then promote downstream. Use the hotfix exception only when unreleased main cannot safely ship.
Stop before a push, production merge, tag, release publication, or branch protection change unless the user explicitly authorized that exact action.

Route the invocation

Interpret $ARGUMENTS as one of these operations. If the operation or version is missing, inspect the repository state and ask only for the decision that cannot be derived safely.

Operation	Outcome
`adopt`	Bootstrap and protect `production`
`integrate`	Merge a feature, fix, or quality improvement into `main`
`promote`	Prove the current release candidate and propose `main -> production`
`cut X.Y.Z`	Prepare, promote, tag, and observe version `X.Y.Z`
`hotfix X.Y.Z`	Patch the released line without pulling unreleased `main` into production

Read the full file on GitHub · 298 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 · 298 lines · 58 tokens per session scan A f5a5fae1a66f

Subscribe to this mod's changes

release is a skill published in the GitHub repository ymm-oss/fsl (21 stars, last pushed 5d ago), licensed Apache-2.0. It adds 58 tokens to every session and 3,816 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-30.

Git and workflow LLM Releases bounded-model-checking formal-methods formal-specification model-checking

flowguard-development-process-flow

Order staged work, freshness, sync, release, and process claims.

liuyingxuvka/FlowGuard · 20 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

release