A command that builds a CHANGELOG.md file from a Git repository's commit history.

Use it to generate changelogs since a tag or across the full history, group changes by category or version, link pull requests, preview output, and choose an output file.

It turns raw commit messages into an organized record of what changed, so users and developers can follow releases more easily.

changelog — Command by alphaaiservice

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/alphaaiservice/cortex/changelog

Clone the repo

git clone --depth 1 https://github.com/alphaaiservice/cortex

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

When invoked 6,156 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.00052	$0.06156
Opus 5	$0.00026	$0.03078
Sonnet 5	$0.00010	$0.01231
Haiku 4.5	$0.00005	$0.00616

Measured yesterday against content hash bf93612070ee, 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 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.

commands/changelog.md · 727 lines

How it starts

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

Auto-Generate Changelog from Git History

$ARGUMENTS = optional flags controlling scope and output format.

Parse $ARGUMENTS to determine:

--since=TAG: Start point for changelog generation (e.g., --since=v1.0.0). If omitted, use the latest git tag as the start point. If no tags exist, include ALL commits.
--format=FORMAT: Output format — keepachangelog (default) or conventional. Keep a Changelog uses Added/Changed/Deprecated/Removed/Fixed/Security sections. Conventional uses emoji-prefixed type categories.
--all: Generate changelog for the entire git history, not just since the last tag.
--dry-run: Print the changelog to stdout without writing to file.
--output=PATH: Custom output path (default: CHANGELOG.md in project root).
--repo-url=URL: Override auto-detected repository URL for commit/PR links.

If no arguments are provided, default to: since last tag, keepachangelog format, write to CHANGELOG.md.

Step 0: Pre-Flight Validation

0a. Verify git repository

git rev-parse --is-inside-work-tree 2>/dev/null

If NOT a git repository:

[ERROR] Not a git repository. Run 'git init' or navigate to a git project first.

STOP immediately.

0b. Check for commits

COMMIT_COUNT=$(git rev-list --count HEAD 2>/dev/null || echo "0")

If zero commits:

[ERROR] No commits found in this repository. Make some commits first.

STOP immediately.

0c. Detect repository URL for linking

REMOTE_URL=$(git remote get-url origin 2>/dev/null || echo "")

Parse the remote URL to construct links:

If github.com: extract OWNER/REPO for GitHub links (https://github.com/OWNER/REPO)
If gitlab.com: extract for GitLab links
If bitbucket.org: extract for Bitbucket links
If --repo-url was provided in $ARGUMENTS, use that instead
If no remote and no override, links will be omitted (local-only mode)

Record:

REPO_URL = the base URL for the repository (e.g., https://github.com/owner/repo)
PLATFORM = github | gitlab | bitbucket | local

Read the full file on GitHub · 727 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 · 727 lines · 52 tokens per session scan A bf93612070ee

Subscribe to this mod's changes

changelog is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 6,156 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-08-31.

Git and workflow Productivity automation claude-code-plugin sdlc

changelog

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Auto-Generate Changelog from Git History

Step 0: Pre-Flight Validation

0a. Verify git repository

0b. Check for commits

0c. Detect repository URL for linking

What this file has done since we first saw it

Other commands, from other repositories

_composicion

alfred

audit

feature

ajustes

discuss