What is changelog-update?

A command that updates CHANGELOG.md from Git commits since the latest version or release. A changelog is a human-readable record of what changed between software versions.

Use it to create a Keep a Changelog section, classify conventional commits, and optionally suggest a semantic version increase.

It removes the need to review commits and manually sort them into additions, fixes, documentation, maintenance, tests, and CI changes.

changelog-update — Command for Claude Code by gonzalezpazmonica

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.

Clone the repo

git clone --depth 1 https://github.com/gonzalezpazmonica/savia

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

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/commands/gonzalezpazmonica/savia/changelog-update/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/savia/changelog-update)

Your own site

<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/changelog-update"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/changelog-update/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/commands/gonzalezpazmonica/savia/changelog-update"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/changelog-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 722 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.

Model	Per session	Once invoked
Fable 5.1	$0.00068	$0.00722
Opus 5	$0.00034	$0.00361
Sonnet 5	$0.00014	$0.00144
Haiku 4.5	$0.00007	$0.00072

Measured 4d ago against content hash cc45eb40d637, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

changelog-update 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

changelog-update — 100% identical, 0 lines differ

.claude/commands/changelog-update.md · 104 lines

How it starts

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

Actualización de CHANGELOG

Analiza los commits desde la última versión y actualiza CHANGELOG.md siguiendo el formato "Keep a Changelog" (https://keepachangelog.com).

Protocolo

1. Identificar la última versión

# Buscar el último tag de versión
git tag --sort=-v:refname | head -5

# Si no hay tags, buscar la última entrada en CHANGELOG.md
head -30 CHANGELOG.md

2. Obtener commits desde la última versión

# Si hay tag
git log v{LAST_VERSION}..HEAD --oneline --no-merges

# Si no hay tag, desde el último cambio del CHANGELOG
git log --oneline --no-merges -50

3. Clasificar commits por tipo

Usando los tipos definidos en docs/rules/domain/github-flow.md:

Tipo	Sección CHANGELOG
`feat`	### Added
`fix`	### Fixed
`docs`	### Documentation
`refactor`	### Changed
`chore`	### Maintenance
`test`	### Testing
`ci`	### CI/CD

Ignorar commits de merge y commits del tipo wip.

4. Generar la nueva sección

Formato de cada entrada:

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

### Added
- Descripción clara del cambio (#PR o commit hash)

### Fixed
- Descripción del bug corregido

### Changed
- Descripción del cambio de comportamiento

5. Sugerir versión semántica

Analizar los commits para proponer el bump:

MAJOR (X.0.0): si hay commits con feat!: o BREAKING CHANGE
MINOR (0.X.0): si hay commits feat: sin breaking changes
PATCH (0.0.X): si solo hay fix:, docs:, chore:

Proponer al humano — NUNCA hacer bump automáticamente.

6. Delegar redacción final

Si el agente tech-writer está disponible, delegar la redacción final para garantizar consistencia de tono y estilo con el resto del CHANGELOG.

7. Presentar al humano

Mostrar la sección generada y preguntar:

¿Versión propuesta es correcta?
¿Alguna entrada necesita ajuste?
¿Procedo a actualizar CHANGELOG.md?

Solo tras confirmación, escribir en el fichero.

Restricciones

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

4d ago First seen · 104 lines · 68 tokens per session scan A cc45eb40d637

Subscribe to this mod's changes

changelog-update is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 722 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-09-06.

Claude Code Git and workflow Releases Writing and docs codex harness opencode

changelog-update