Borrowing it
Nothing to install: this file belongs to guess/claude_code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/guess/claude_code/main/.claude/commands/update-changelog.mdgit clone --depth 1 https://github.com/guess/claude_codeWrote 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.
[](https://agentmods.dev/commands/guess/claude_code/update-changelog)<a href="https://agentmods.dev/commands/guess/claude_code/update-changelog"><img src="https://agentmods.dev/badge/commands/guess/claude_code/update-changelog/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.
<a href="https://agentmods.dev/commands/guess/claude_code/update-changelog"><img src="https://agentmods.dev/badge/commands/guess/claude_code/update-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00009 | $0.01295 |
| Opus 5.5 | $0.00004 | $0.00518 |
| Sonnet 5.5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
update-changelog 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Changelog
This command automatically updates the CHANGELOG.md file by analyzing git commits since the last changelog update.
Usage
/update-changelog
Description
This command will:
- Check if a CHANGELOG.md file exists
- If not found, create one with the standard Keep a Changelog header
- Find the last commit referenced in the changelog (or start from the beginning if none)
- Fetch all commits since that reference
- Parse each commit message to extract:
- The gitmoji and/or conventional commit type (feat, fix, chore, etc.)
- The commit description
- The commit hash (short form)
- Filter commits to include ONLY user-facing changes (see filtering rules below)
- Group commits by type into changelog sections:
- ✨ feat → Added
- 🐛 fix, 🚑️ hotfix → Fixed
- ♻️ refactor, 🎨 style → Changed
- 🗑️ deprecate → Deprecated
- 🔥 remove → Removed
- 🔒️ security → Security
- All other types → Other Changes
- Add entries to the "Unreleased" section at the top of the changelog
- Format entries as:
- Description ([commit-hash])
What to Include vs Exclude
IMPORTANT: The changelog is for library USERS, not developers. Only document changes that affect how users interact with or use the library.
✅ SHOULD Include
Changes that affect library users:
- New features - New public APIs, functions, modules, options
- Bug fixes - Fixes to public API behavior or user-facing issues
- Breaking changes - Changes to public APIs, function signatures, behavior
- Deprecations - Deprecated public APIs or features
- Performance improvements - User-visible performance changes
- Documentation - Updates to README, guides, or public API docs that help users
- Dependencies - Changes to runtime dependencies that users need to know about
❌ SHOULD NOT Include
Internal changes that don't affect library users:
- Internal tooling - Changes to
.claude/configs, slash commands, AI prompts - Development infrastructure - CI/CD configs, test scripts, build tools
- Internal refactoring - Code reorganization without API changes
- Development dependencies - Changes to dev/test-only dependencies
- Proposals and planning - Design docs, proposals, roadmaps in
docs/ - Internal documentation - CLAUDE.md, development notes, architecture docs for contributors
- Code style/formatting - Formatting changes, linting fixes without functional changes
- Test code - Test additions or changes (unless they reveal new features)
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.
- 2mo ago First seen · 128 lines · 9 tokens per session scan A fad59e5fd5fd
update-changelog is a command published in the GitHub repository guess/claude_code (98 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,295 once invoked, about $0.0000 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.
Other commands, from other repositories
caveman-commit
Generate a terse caveman-style commit message for staged changes.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit
A command that checks staged Git changes and creates a commit from them.