What is changelog-generator?

A tool for turning Conventional Commits—structured commit messages—into consistent release notes. It can also determine whether the next version is a major, minor, or patch release and check commit formatting.

Use it before releases, in continuous integration checks, during pull-request validation, and in monorepos, where one repository contains multiple packages.

It removes the manual work and inconsistency of turning Git history into user-facing changelogs. Editorial control remains available before notes are published.

changelog-generator — Skill for Codex by bestagentkits

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 bestagentkits/agency-skills --skill changelog-generator

Clone the repo

git clone --depth 1 https://github.com/bestagentkits/agency-skills

Made for: Codex.

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/bestagentkits/agency-skills/changelog-generator/github.svg)](https://agentmods.dev/skills/bestagentkits/agency-skills/changelog-generator)

Your own site

<a href="https://agentmods.dev/skills/bestagentkits/agency-skills/changelog-generator"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/changelog-generator/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bestagentkits/agency-skills/changelog-generator"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/changelog-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,758 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.

Model	Per session	Once invoked
Fable 5.1	$0.00107	$0.01758
Opus 5	$0.00053	$0.00879
Sonnet 5	$0.00021	$0.00352
Haiku 4.5	$0.00011	$0.00176

Measured 9d ago against content hash 783ecfdcb6b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

changelog-generator 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 9d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/commit_linter.py, scripts/generate_changelog.py, scripts/version_bumper.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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

changelog-generator — 97% identical, 7 lines differ

skills/claude-skills/changelog-generator/SKILL.md · 204 lines

How it starts

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

Changelog Generator

Tier: POWERFUL
Category: Engineering
Domain: Release Management / Documentation

Overview

Use this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.

Core Capabilities

Parse commit messages using Conventional Commit rules
Detect semantic bump (major, minor, patch) from commit stream
Render Keep a Changelog sections (Added, Changed, Fixed, etc.)
Generate release entries from git ranges or provided commit input
Enforce commit format with a dedicated linter script
Support CI integration via machine-readable JSON output

When to Use

Before publishing a release tag
During CI to generate release notes automatically
During PR checks to block invalid commit message formats
In monorepos where package changelogs require scoped filtering
When converting raw git history into user-facing notes

Key Workflows

1. Generate Changelog Entry From Git

python3 scripts/generate_changelog.py \
  --from-tag v1.3.0 \
  --to-tag v1.4.0 \
  --next-version v1.4.0 \
  --format markdown

2. Generate Entry From stdin/File Input

git log v1.3.0..v1.4.0 --pretty=format:'%s' | \
  python3 scripts/generate_changelog.py --next-version v1.4.0 --format markdown

python3 scripts/generate_changelog.py --input commits.txt --next-version v1.4.0 --format json

3. Update `CHANGELOG.md`

python3 scripts/generate_changelog.py \
  --from-tag v1.3.0 \
  --to-tag HEAD \
  --next-version v1.4.0 \
  --write CHANGELOG.md

4. Compute the Next Version From Commits

When the user has not decided the next version, derive it instead of guessing:

git log v1.3.0..HEAD --oneline | \
  python3 scripts/version_bumper.py --current-version 1.3.0 --output-format json

Output JSON contains recommended_version, bump_type (major/minor/patch/none), and with --include-commands the exact git tag commands. Feed recommended_version into generate_changelog.py --next-version. Pre-releases: add --prerelease alpha|beta|rc. Input must be real git log --oneline output (hex hashes); a sample lives at assets/sample_git_log.txt.

Read the full file on GitHub · 204 lines

Files

What ships with it

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

9d ago First seen · 204 lines · 107 tokens per session scan A 783ecfdcb6b2

Subscribe to this mod's changes

changelog-generator is a skill published in the GitHub repository bestagentkits/agency-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,758 once invoked, about $0.0005 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-09-03.

Git and workflow Releases Writing and docs agentskills claude claudecode codex skills

apply-semantic-versioning

Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…

pjt222/agent-almanac · 94 tokens

create-github-release

Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…

pjt222/agent-almanac · 73 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…

addyosmani/agent-skills · 89 tokens

comet-archive

A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.

rpamis/comet · 33 tokens

finishing-a-development-branch

A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.

jnMetaCode/superpowers-zh · 25 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens