New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Changelog Generator

by alirezarezvani in alirezarezvani/claude-skills

Produce consistent, auditable release notes from Conventional Commits.

MITAuto-check passedDevelopment

Install Changelog Generator

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill changelog-generator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills changelog-generator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/skills/changelog-generator .claude/skills/changelog-generator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
changelog-generator
GitHub stars
28k
Token cost
~1.9k tokens
SKILL.md length
707 words
Files
10 (incl. scripts, references, assets)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Produce consistent, auditable release notes from Conventional Commits.

  • Works in 5 steps: Generate Changelog Entry From Git → Generate Entry From stdin/File Input → Update CHANGELOG.md → …
  • Cutting a release
  • SKILL.md covers Overview, Core Capabilities, When to Use and Key Workflows, plus 12 more sections
  • Runs Python scripts from its folder; calls python3 and git

What it does

Changelog Generator is an agent skill from alirezarezvani/claude-skills. Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `README.md`, `references/changelog-formatting-guide.md` and `references/ci-integration.md`).

It sits in Development, covering Changelog and release notes, Commit messages and Git workflow. It works with Git. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Cutting a release
  • Generating CHANGELOG.md from git history
  • Computing the next semantic version from commits
  • Automating release notes in CI

Example prompts

  • “generate the changelog for v1.4.0”
  • “what version bump do these commits require”
  • “we need an emergency hotfix process”
  • “/changelog-generator”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Generate Changelog Entry From Git
  2. Generate Entry From stdin/File Input
  3. Update CHANGELOG.md
  4. Compute the Next Version From Commits
  5. Lint Commits Before Merge

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changelog Generator loads about 1.9k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 707 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~131
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 707 words, ~1,879 tokens.

Download SKILL.mdSave it as .claude/skills/changelog-generator/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
changelog-generator
description
Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'.

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
bash
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
bash
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
bash
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:

bash
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.

5. Lint Commits Before Merge
bash
python3 scripts/commit_linter.py --from-ref origin/main --to-ref HEAD --strict --format text

Or file/stdin:

bash
python3 scripts/commit_linter.py --input commits.txt --strict
cat commits.txt | python3 scripts/commit_linter.py --format json

Conventional Commit Rules

Supported types:

  • feat, fix, perf, refactor, docs, test, build, ci, chore
  • security, deprecated, remove

Breaking changes:

  • type(scope)!: summary
  • Footer/body includes BREAKING CHANGE:

SemVer mapping:

  • breaking -> major
  • non-breaking feat -> minor
  • all others -> patch

Script Interfaces

  • python3 scripts/generate_changelog.py --help
    • Reads commits from git or stdin/--input
    • Renders markdown or JSON
    • Optional in-place changelog prepend
  • python3 scripts/commit_linter.py --help
    • Validates commit format
    • Returns non-zero in --strict mode on violations

Common Pitfalls

  1. Mixing merge commit messages with release commit parsing
  2. Using vague commit summaries that cannot become release notes
  3. Failing to include migration guidance for breaking changes
  4. Treating docs/chore changes as user-facing features
  5. Overwriting historical changelog sections instead of prepending

Best Practices

  1. Keep commits small and intent-driven.
  2. Scope commit messages (feat(api): ...) in multi-package repos.
  3. Enforce linter checks in PR pipelines.
  4. Review generated markdown before publishing.
  5. Tag releases only after changelog generation succeeds.
  6. Keep an [Unreleased] section for manual curation when needed.

Hotfix Severity & SLAs

When a release goes wrong, classify before acting (full procedures in references/hotfix-procedures.md):

SeverityDefinitionSLAApproval
P0 — CriticalOutage, data loss, exploited vulnerabilityFix deployed ≤ 2h; emergency deploy bypasses normal gatesEngineering Lead + On-call Manager
P1 — HighMajor feature broken, significant user impactFix deployed ≤ 24h; expedited reviewEngineering Lead + Product Manager
P2 — MediumMinor issues, limited impactNext release cycleStandard PR review

Hotfix branch comes from the last stable tag, contains the minimal fix only, and gets its own patch-bump changelog entry via the workflow above.

Show full SKILL.md (240 more words)Show less

Rollback Triggers

Pre-commit to these thresholds before tagging; roll back when any fires:

TriggerThreshold
Error rate spike> 2x baseline within 30 min
Performance degradation> 50% latency increase
Feature failureCore functionality broken
Security incidentVulnerability being exploited
Data corruptionDatabase integrity compromised

Prefer feature-flag disable over code rollback; database rollbacks only for non-destructive migrations (forward-only migrations preferred). See references/hotfix-procedures.md.

References

Release Governance

Use this release flow for predictability:

  1. Lint commit history for target release range.
  2. Generate changelog draft from commits.
  3. Manually adjust wording for customer clarity.
  4. Validate semver bump recommendation.
  5. Tag release only after changelog is approved.

Output Quality Checks

  • Each bullet is user-meaningful, not implementation noise.
  • Breaking changes include migration action.
  • Security fixes are isolated in Security section.
  • Sections with no entries are omitted.
  • Duplicate bullets across sections are removed.

CI Policy

  • Run commit_linter.py --strict on all PRs.
  • Block merge on invalid conventional commits.
  • Auto-generate draft release notes on tag push.
  • Require human approval before writing into CHANGELOG.md on main branch.

Monorepo Guidance

  • Prefer commit scopes aligned to package names.
  • Filter commit stream by scope for package-specific releases.
  • Keep infra-wide changes in root changelog.
  • Store package changelogs near package roots for ownership clarity.

Failure Handling

  • If no valid conventional commits found: fail early, do not generate misleading empty notes.
  • If git range invalid: surface explicit range in error output.
  • If write target missing: create safe changelog header scaffolding.

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in engineering/skills/changelog-generator of alirezarezvani/claude-skills.

  • SKILL.md
  • README.md
  • assets/sample_git_log.txt
  • references/changelog-formatting-guide.md
  • references/ci-integration.md
  • references/hotfix-procedures.md
  • references/monorepo-strategy.md
  • scripts/commit_linter.py
  • scripts/generate_changelog.py
  • scripts/version_bumper.py

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Changelog Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changelog Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changelog Generator this skillalirezarezvani/claude-skills28k—~1.9kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills104k2 repos~3.5kAutomated safety check: NotesMIT
WooCommerce Git Commitwoocommerce/woocommerce11k—~1.2kAutomated safety check: PassCustom licence
Git Changes ReporterNo-Trade-No-Life/Yuan352—~1.2kAutomated safety check: PassMIT
Shift Commit Rulesshift-editor/shift349—~1.4kAutomated safety check: NotesApache-2.0
Version Bump and ReleaseescapeWu/perplexity-ai171—~528Automated safety check: PassMIT

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    104k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • WooCommerce Git Commit

    woocommerce/woocommerce

    Commits pending changes with short, verb-first messages that follow WooCommerce repository conventions, splitting commits only when changes are clearly unrelated.

    11k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Changes Reporter

    No-Trade-No-Life/Yuan

    生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。

    352 GitHub stars~1.2k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Shift Commit Rules

    shift-editor/shift

    Rules for writing git commits in the Shift font editor repo: Conventional Commits subjects, user-facing changelog wording, concise subjects and logical commit boundaries.

    349 GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check: notes

  • Version Bump and Release

    escapeWu/perplexity-ai

    Bumps a project version, updates both changelogs, builds the frontend, then commits, tags and pushes the release.

    171 GitHub stars~528 tokensUpdated 13 days ago
    DevelopmentAuto-check passed

  • Changelog Generator for Java

    decebals/claude-code-java

    Builds changelog entries from conventional commits in a Java project, after working out whether it uses SemVer, two-part versions or calendar versions.

    751 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed

  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Works with

Categories

Questions about Changelog Generator

What does Changelog Generator do?

Produce consistent, auditable release notes from Conventional Commits. Changelog Generator is an agent skill from alirezarezvani/claude-skills. Produce consistent, auditable release notes from Conventional Commits.

When should I use Changelog Generator?

Changelog Generator fits situations like: cutting a release; generating CHANGELOG.md from git history; computing the next semantic version from commits; automating release notes in CI.

How do I install Changelog Generator in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill changelog-generator -a claude-code`. Or copy the skill folder (engineering/skills/changelog-generator in alirezarezvani/claude-skills) into .claude/skills/changelog-generator in your project. Claude Code loads it when a task matches its description.

How do I install Changelog Generator in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill changelog-generator -a codex`. Or copy the skill folder (engineering/skills/changelog-generator in alirezarezvani/claude-skills) into .agents/skills/changelog-generator in your project. Codex loads it when a task matches its description.

Can I use Changelog Generator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill changelog-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changelog-generator, .gemini/skills/changelog-generator, .github/skills/changelog-generator and .opencode/skills/changelog-generator in your project.

What does Changelog Generator need to run?

Going by SKILL.md and its folder, Changelog Generator needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.

Does Changelog Generator access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Changelog Generator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Changelog Generator use?

Changelog Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changelog Generator use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Changelog Generator?

Skills that share tags, products or a category with Changelog Generator: Git Workflow and Versioning (addyosmani/agent-skills, 104k stars), WooCommerce Git Commit (woocommerce/woocommerce, 11k stars), Git Changes Reporter (No-Trade-No-Life/Yuan, 352 stars) and Shift Commit Rules (shift-editor/shift, 349 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog Generator?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.