A changelog generator that reads Git history and organizes changes into Keep a Changelog sections such as Added, Fixed, Security, and Breaking Changes.

Use it before a release or when documenting work since a tag. It can process the latest release range, all unreleased commits, or a specified reference.

It turns commit history into release notes, reducing the manual work of finding and categorizing changes.

changelog — Skill for Claude Code by viknesh20-20: A changelog generator that reads Git history and organizes…

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/viknesh20-20/claude-code-tool-kit/changelog

Any agent

npx skills add viknesh20-20/claude-code-tool-kit --skill changelog

Clone the repo

git clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kit

Made for: Claude Code.

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/skills/viknesh20-20/claude-code-tool-kit/changelog.svg)](https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/changelog)

Your own site

<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/changelog"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/changelog.svg" alt="Measured on agentmods" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 691 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.1	$0.00045	$0.00691
Opus 5	$0.00023	$0.00345
Sonnet 5	$0.00009	$0.00138
Haiku 4.5	$0.00005	$0.00069

Measured 6d ago against content hash 0675b2eb50a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

.claude/skills/changelog/SKILL.md · 97 lines

How it starts

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

Generate Changelog

Git History

!git log --oneline --no-merges -50 2>/dev/null

Latest Tag

!git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"

Instructions

Step 1: Determine Range

If a tag/ref is provided, use: git log <tag>..HEAD
If "last-release" is specified, find the most recent tag
If "unreleased" or no argument, show all commits since last tag

Step 2: Gather Commits

Run: git log <range> --oneline --no-merges

For each commit, extract:

Commit hash (short)
Commit message
Author
Date
PR number (if referenced)

Step 3: Categorize

Group commits using Keep a Changelog categories:

Added: New features, endpoints, commands, pages
Changed: Modifications to existing functionality, API changes
Fixed: Bug fixes, error corrections
Deprecated: Features marked for removal
Removed: Deleted features, removed dependencies
Security: Vulnerability fixes, security improvements
Breaking Changes: Changes that require consumer updates

Detection heuristics:

feat: / feature: / add: → Added
fix: / bugfix: / hotfix: → Fixed
refactor: / update: / change: → Changed
remove: / delete: / drop: → Removed
security: / vuln: / cve: → Security
BREAKING: / BREAKING CHANGE: → Breaking Changes
Other: categorize by reading the commit message

Step 4: Format Output

# Changelog

## [Unreleased] — YYYY-MM-DD

### Added
- Description of new feature (#PR)

### Changed
- Description of change (#PR)

### Fixed
- Description of fix (#PR)

### Removed
- Description of removal (#PR)

### Security
- Description of security fix (#PR)

### Breaking Changes
- Description of breaking change (#PR)

Step 5: Save or Display

If a CHANGELOG.md exists, prepend the new section
If not, create a new CHANGELOG.md
Always show the generated content for review before saving

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

6d ago First seen · 97 lines · 45 tokens per session scan A 0675b2eb50a9

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 691 once invoked, about $0.0002 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 agent-orchestration ai-agents ai-coding-assistant-tools ai-development-toolkit claude-ai-skills claude-code

gh-credit-harvest

Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.

Hmbown/CodeWhale · 30 tokens

release

Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness. Publishing/tagging/deploy need separate authorization. Explicit-only.

Hmbown/CodeWhale · 0 tokens

herdr-pre-release-audit

Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.

herdrdev/herdr · 65 tokens

tutti-app-release

Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…

tutti-os/tutti · 80 tokens

git-integration

Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.

a5c-ai/babysitter · 39 tokens

helmor-bump-vendors

Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab / cloudflared / llama.cpp / Node. Encodes exactly which files to edit (sidecar/package.json…

dohooo/helmor · 185 tokens

changelog