changelog

changelog is a skill for Claude Code from ekline-io/ekline-docs-skills. It costs 59 tokens per session (683 once invoked), scanned A, original, MIT.

A tool that creates a structured changelog, which is a record of notable project changes, from Git history.

In plain words
What is it for?
It is for preparing Keep a Changelog entries before a release or for reviewing changes over a selected commit range.
Why use it?
It helps fill in missing release notes and group commits into categories such as additions, fixes, and breaking changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ekline-docs-skills plugin — 6 skills shipped together

Good fit It is for preparing Keep a Changelog entries before a release or for reviewing changes over a selected commit range.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ekline-io/ekline-docs-skills/changelog
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.

Any agent
npx skills add ekline-io/ekline-docs-skills --skill changelog
Clone the repo
git clone --depth 1 https://github.com/ekline-io/ekline-docs-skills

Made for: Claude Code.

Or install ekline-docs-skills, the plugin that ships this one along with the rest of its 6 skills.

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.

agentmods badge for changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/changelog/github.svg)](https://agentmods.dev/skills/ekline-io/ekline-docs-skills/changelog)
Your own site
<a href="https://agentmods.dev/skills/ekline-io/ekline-docs-skills/changelog"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/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.

agentmods 80×15 button for changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/ekline-io/ekline-docs-skills/changelog"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 683 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00059 $0.00683
Opus 5 $0.00030 $0.00342
Sonnet 5 $0.00012 $0.00137
Haiku 4.5 $0.00006 $0.00068

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/parse_commits.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/changelog/SKILL.md · 109 lines

How it starts

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

Generate changelog

Run the helper script to parse git history, then present and optionally write the results.

Inputs

  • $ARGUMENTS — optional version tag or commit range (e.g., v1.3.0, v1.2.0..v1.3.0, HEAD~20..HEAD)

Steps

1. Run the helper script

python scripts/parse_commits.py $ARGUMENTS

Capture the JSON output. The script handles range detection, commit parsing, conventional commit classification, keyword heuristics, PR/issue extraction, and deduplication.

Max 200 commits per run.

2. Handle errors

If the JSON contains an error field:

  • not_a_git_repo — tell user to run from inside a git repository
  • no_commits — tell user no commits were found in the given range, suggest a different range

Stop here on error.

3. Present the changelog entry

Using the categories object from the JSON, format a Keep a Changelog entry:

## [Unreleased] - YYYY-MM-DD

### Breaking Changes
- {text from entries}

### Added
- {text from entries}

### Changed
- {text from entries}

### Fixed
- {text from entries}

### Removed
- {text from entries}

### Security
- {text from entries}

Only include categories that have entries. Use the text field from each entry directly — the script already formats entries with imperative mood and PR references.

Show the user:

  • Number of commits analyzed (total_commits_analyzed)
  • Number of entries generated (total_changelog_entries)
  • Number skipped as internal (total_skipped)
  • The full formatted entry

4. Ask the user

Ask whether they want to:

  1. Write the entry to CHANGELOG.md
  2. Just see the output (done)

5. Write to CHANGELOG.md

If the user wants to write:

If CHANGELOG.md exists:

  • Read it with the Read tool
  • Insert the new entry after the file header (before the first ## [ line)
  • Preserve all existing content

If CHANGELOG.md does not exist:

  • Create it with the standard header:
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

{generated entry here}

Read the full file on GitHub · 109 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 109 lines · 59 tokens per session scan A 9c9d8b06a88d

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository ekline-io/ekline-docs-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 683 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.