What is update-changelog-and-tag?

A release-preparation command that reads commits since the latest Git tag, updates the changelog, and creates the next version tag.

Use it to prepare a minor, patch, or major release and group changes under headings such as Added, Fixed, and Security.

It organizes release notes and version numbers from the work already recorded in Git, reducing manual release preparation.

update-changelog-and-tag — Command by sandst1

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/sandst1/remind/update-changelog-and-tag

Clone the repo

git clone --depth 1 https://github.com/sandst1/remind

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 695 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.00695
Opus 5	$0.00000	$0.00347
Sonnet 5	$0.00000	$0.00139
Haiku 4.5	$0.00000	$0.00069

Measured yesterday against content hash 1e0076b377bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-changelog-and-tag 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 yesterday.

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/update-changelog-and-tag.md · 89 lines

How it starts

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

Release: Update Changelog and Tag

You are preparing a release. Follow these steps precisely.

1. Determine release type

Default to minor unless the user specified patch or major in their request.

2. Get latest tag and commits since it

Run:

git describe --tags --abbrev=0

Then get all commits since that tag:

git log <latest-tag>..HEAD --oneline

Also get the full commit messages for context:

git log <latest-tag>..HEAD --pretty=format:"%h %s%n%b"

3. Compute new version

Parse the latest tag (strip leading v if present) as MAJOR.MINOR.PATCH.

major: increment MAJOR, reset MINOR and PATCH to 0
minor: increment MINOR, reset PATCH to 0
patch: increment PATCH only

4. Categorize commits

Read through the commit messages and group changes under the standard Keep-a-Changelog headings:

Added – new features
Changed – changes to existing behavior
Deprecated – soon-to-be-removed features
Removed – removed features
Fixed – bug fixes
Security – security fixes

Omit any heading that has no entries. Write concise, user-facing bullet points (not git commit hashes).

5. Update CHANGELOG.md

Open CHANGELOG.md. Replace the ## [Unreleased] section (keep the heading) and insert a new versioned section above the previous release, using today's date (YYYY-MM-DD). Keep the ## [Unreleased] heading empty above it for future use.

Format:

## [Unreleased]

## [X.Y.Z] - YYYY-MM-DD

### Added
- ...

### Fixed
- ...

6. Update version in pyproject.toml

Find the version field in pyproject.toml and update it to the new version string.

7. Sync documentation site

website/reference/changelog.md — Mirror the same new version section you added to CHANGELOG.md (same date and bullets; keep the site’s existing formatting style, e.g. bold labels on list items if present).
website/.vitepress/config.ts — In themeConfig.nav, find the dropdown whose items include Changelog and PyPI. Set its text to vX.Y.Z (must match the release tag). This is the version shown in the top-right corner of the docs site.

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

yesterday First seen · 89 lines · 0 tokens per session scan A 1e0076b377bc

Subscribe to this mod's changes

update-changelog-and-tag is a command published in the GitHub repository sandst1/remind (83 stars, last pushed 22d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 695 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 Memory and context Security agentic-ai agents ai coding context-engineering genai

dedupe

You are a GitHub issue deduplication assistant. Your job is to determine if a given issue is a duplicate of an existing issue.

VectifyAI/PageIndex · 0 tokens

api-mock

You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.

wshobson/agents · 0 tokens

update-changelog-and-tag