A command workflow that summarizes commits since the latest version tag in the Unreleased section of CHANGELOG.md. A changelog records user-facing changes between software versions.

Use it to prepare a release draft from repository history, including features, fixes, security changes, and contributor credits. After explicit confirmation, it updates the version and follows the release steps.

It removes the need to manually inspect every commit and helps organize changes into standard categories before asking for release approval.

release — Command by yoshiko-pg

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 commands/yoshiko-pg/difit/release

Clone the repo

git clone --depth 1 https://github.com/yoshiko-pg/difit

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 366 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.00000	$0.00366
Opus 5	$0.00000	$0.00183
Sonnet 5	$0.00000	$0.00073
Haiku 4.5	$0.00000	$0.00037

Measured 2d ago against content hash 906e824afeed, 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/commands/release.md · 35 lines

What it actually says

Update CHANGELOG.md with all changes from the latest tag to current commit.

First, run the script to get commit information:

./scripts/get-changes-since-tag.sh

Use the script output to categorize changes:

Added for new features.
Changed for changes in existing functionality.
Deprecated for soon-to-be removed features.
Removed for now removed features.
Fixed for any bug fixes.
Security in case of vulnerabilities.
Thanks for contributors mention with GitHub username and PR number

When processing commits:

Use the GitHub username from script output (not git commit author names)
Only include contributors in Thanks section (exclude yoshiko-pg as that's the maintainer, and exclude renovate[bot])
Include PR numbers when available
Use commit subject and body to properly categorize changes

Write the categorized changes to the Unreleased section of CHANGELOG.md, then inform the user in Japanese and ask for confirmation. (Don't just output the changes - write them to the file first so the user can review the actual file.)

If confirmed OK:

npm version --no-git-tag-version patch
Treat the Unreleased section as-is at the time of user OK as the single source of truth. Do not regenerate, re-categorize, or overwrite it after the OK signal.
Create a version section in CHANGELOG.md and move Unreleased section content there
Update the version links at the bottom of CHANGELOG.md (add new version links and update Unreleased link)
Commit CHANGELOG.md
create current version git tag
git push origin main --tags
create release on github with CHANGELOG.md target version section text (to origin)

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 · 35 lines · 0 tokens per session scan A 906e824afeed

Subscribe to this mod's changes

release is a command published in the GitHub repository yoshiko-pg/difit (3,122 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 tokens. 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

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

review-renovate

release

release

SHIP_RELEASE

release

release