A changelog command that creates a document describing recent project changes in a Problem/Solution format. A changelog is a record of what changed between software versions or development sessions.

Use it to document files changed, features added, bugs fixed, and other recent work, with model selection available when no project preference is set.

It gathers recent work from the current session and checks Git history to reduce omissions and duplicate entries. It can also use a project-level preference for the language model used to generate the document.

changelog — Command by scarrillo

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/scarrillo/release/changelog

Clone the repo

git clone --depth 1 https://github.com/scarrillo/release

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

When invoked 2,283 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.00011	$0.02283
Opus 5	$0.00005	$0.01141
Sonnet 5	$0.00002	$0.00457
Haiku 4.5	$0.00001	$0.00228

Measured 2d ago against content hash ea34edd78f9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

commands/changelog.md · 258 lines

How it starts

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

Changelog Generator

Generate a comprehensive changelog document based on recent changes in this project.

Model Selection

Before generating the changelog, check for model preference:

Check config for release-plugin.model setting
If not set, ask the user: "Which model should I use for changelog generation?"
1. Current model (inherit from conversation)
2. Claude Opus 4.5 (claude-opus-4-5-20251101) - Most capable
3. Claude Sonnet 4 (claude-sonnet-4-20250514) - Balanced (Recommended)
4. Claude Haiku 3.5 (claude-3-5-haiku-20241022) - Fastest
Then ask: "Save this as default for this project?"
- If yes, persist to .claude/config.json under release-plugin.model

Note: Model selection applies to all plugin commands (changelog, decisions, whattotest).

Instructions

Analyze recent changes using this priority order:

Primary source - Current session:
- Review all work completed in this conversation session
- Include files created, modified, features implemented, and bugs fixed
- This is the most accurate and detailed source of recent work
Cross-reference with git to deduplicate:
- Check recent git commit history (git log)
- Check staged changes (git diff --staged)
- Check unstaged changes (git diff)
- Use git data to verify session work and avoid duplicate entries
- If work from the session has already been committed, use the commit info to enrich the changelog entry (commit hash, timestamp)
Handle uncommitted session work:
- If session work is not yet committed, ask the user:
  1. "Commit first" - Let the user commit their changes, then proceed
  2. "Include uncommitted" - Generate changelog including uncommitted session work
  3. "Skip uncommitted" - Only include work that has been committed
Reference existing changelogs:
- Check any existing changelog files for format consistency and to avoid re-documenting old changes
Categorize changes into:
- Features: New functionality added
- Improvements: Enhancements to existing features
- Bug Fixes: Issues that were resolved
- Breaking Changes: Changes that may affect existing functionality (if any)

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

2d ago First seen · 258 lines · 11 tokens per session scan A ea34edd78f9b

Subscribe to this mod's changes

changelog is a command published in the GitHub repository scarrillo/release (9 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 2,283 once invoked, about $0.0001 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-08-31.

Git and workflow Releases Writing and docs

changelog

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Changelog Generator

Model Selection

Instructions

What this file has done since we first saw it

Other commands, from other repositories

review-renovate

release

release

SHIP_RELEASE

release

release