A release guide that uses merged Git changes to suggest a version number, draft a changelog, and prepare release commands. A changelog is a human-readable record of what changed.

Use it when shipping a release, creating a Git tag, updating CHANGELOG.md, or generating release notes from conventional commits such as feat and fix.

Releases are easier to get wrong when version numbers, notes, and Git tags are prepared manually. It provides a consistent way to turn completed changes into a release.

git-release — Skill for Claude Code and Codex by DVNghiem/FlowDeck

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 DVNghiem/FlowDeck --skill git-release

Clone the repo

git clone --depth 1 https://github.com/DVNghiem/FlowDeck

Made for: Claude Code, Codex.

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/dvnghiem/flowdeck/git-release/github.svg)](https://agentmods.dev/skills/dvnghiem/flowdeck/git-release)

Your own site

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

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

When invoked 680 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00035	$0.00680
Opus 5.5	$0.00014	$0.00272
Sonnet 5.5	$0.00007	$0.00136
Haiku 4.5	$0.00003	$0.00068

Measured 1mo ago against content hash b659b2697379, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-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 1mo 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.

src/skills/git-release/SKILL.md · 95 lines

How it starts

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

Git Release Skill

Creates releases with consistent versioning, accurate changelogs, and proper tagging.

When to Activate

Activate when:

A release is complete and ready to ship
You need to cut a release tag
You need to generate a CHANGELOG entry

Core Principles

Semver strictly: major.minor.patch
Conventional commits drive the version bump automatically
Changelog is for humans: group by type, use plain language
One release per tag — no force-pushing tags

Workflow

Collect commits — git log [last-tag]..HEAD --oneline
Determine version bump from commits:
- Breaking change (! or BREAKING CHANGE:) → major bump
- feat: → minor bump
- fix:, refactor:, perf: → patch bump
- docs:, test:, chore: → no version bump (unless last release)
Draft changelog — group commits by type
Update CHANGELOG.md — prepend new version under ## Unreleased
Tag and push — provide the exact commands

Conventional Commits Types

Type	Version Bump	Description
`feat`	minor	New feature
`fix`	patch	Bug fix
`perf`	patch	Performance improvement
`refactor`	patch	Code change, no behavior change
`docs`	none	Documentation only
`test`	none	Adding or updating tests
`chore`	none	Maintenance, dependencies
`ci`	none	CI/CD configuration
`feat!` or `BREAKING CHANGE:`	major	Breaking API change

Changelog Format

Follow Keep a Changelog (keepachangelog.com):

## [1.2.0] — 2024-01-15

### Added
- User authentication via JWT (feat: add JWT auth)
- Password reset via email (feat: add password reset)

### Fixed
- Token expiry calculation was off by one day (fix: correct token expiry)

### Changed
- Migrated from bcrypt to argon2 for better security (refactor: use argon2)

Release Commands

# After updating CHANGELOG.md
git add CHANGELOG.md
git commit -m "chore(release): v1.2.0"
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags

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

1mo ago First seen · 95 lines · 35 tokens per session scan A b659b2697379

Subscribe to this mod's changes

git-release is a skill published in the GitHub repository DVNghiem/FlowDeck (36 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 5.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 Orchestration Releases agentic-ai ai-agents opencode opencode-plugin

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 103 tokens

git-release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Git Release Skill

When to Activate

Core Principles

Workflow

Conventional Commits Types

Changelog Format

Release Commands

What this file has done since we first saw it

Other skills, from other repositories

agent-framework-py-release

worktrees

github-release-management

github-release-management

github-release-management

github-release-management