changelog

A command that creates a changelog from Git history and version tags. A changelog is a readable record of features, fixes, documentation changes, and other updates between releases.

In plain words
What is it for?
Use it to inspect tags and commits, find changes between releases, identify conventional commit types and breaking changes, and generate a changelog.md file.
Why use it?
It saves time when summarizing what changed since the previous release and organizes changes by version and category.

Skill for Claude CodeCodexCursor

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 skills/usrrname/cursorrules/changelog
Any agent
npx skills add usrrname/cursorrules --skill changelog
Clone the repo
git clone --depth 1 https://github.com/usrrname/cursorrules

Made for: Claude Code, Codex, Cursor.

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 472 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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00472
Opus 5 $0.00005 $0.00236
Sonnet 5 $0.00002 $0.00094
Haiku 4.5 $0.00001 $0.00047

Measured 2d ago against content hash e96497a7530e, 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.

.cursor/skills/changelog/SKILL.md ยท 71 lines

What it actually says

Changelog Generation Command ๐Ÿ“

Generate a changelog.md by analyzing git history and tags.

Git Commands

# Get all tags sorted by version (newest first)
git tag --sort=-version:refname

# Get the most recent tag
git describe --tags --abbrev=0

# Get unreleased commits since last tag
git log --oneline --no-merges $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD

# Get commits between two tags
git log --oneline --no-merges <prev-tag>..<current-tag>

# Get tag creation date
git log -1 --format=%ai <tag-name>

Loop Through All Tags

ALL_TAGS=$(git tag --sort=-version:refname)

for tag in $ALL_TAGS; do
  PREV_TAG=$(git describe --tags --abbrev=0 $tag^ 2>/dev/null || echo "")
  COMMITS=$(git log --oneline --no-merges $PREV_TAG..$tag)
  echo "Version $tag:"
  echo "$COMMITS"
  echo "---"
done

Filter by Conventional Commit Type

# Features
git log --oneline --grep="^feat:" <tag1>..<tag2>

# Bug fixes
git log --oneline --grep="^fix:" <tag1>..<tag2>

# Documentation
git log --oneline --grep="^docs:" <tag1>..<tag2>

# Breaking changes
git log --oneline --grep="BREAKING" <tag1>..<tag2>

Generate Changelog

Run these commands and format output following Keep a Changelog format:

  1. Analyze all git tags
  2. Categorize commits by type (feat, fix, docs, chore, etc.)
  3. Create sections: Added, Fixed, Changed, Documentation
  4. Include unreleased changes at the top
  5. Store at project root as changelog.md

See .cursor/rules/utils/changelog-generator-manual.mdc for full formatting rules.

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.

  1. 2d ago First seen ยท 71 lines ยท 9 tokens per session scan A e96497a7530e

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 9 tokens to every session and 472 once invoked, about $0.0000 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.