Agent skill · Documentation

changelog-generator

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

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill changelog-generator --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 10
SKILL.md size: 7 KB
Bundled scripts: yes
Path: engineering/skills/changelog-generator/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Overview
  2. Core Capabilities
  3. When to Use
  4. Key Workflows
  5. 1. Generate Changelog Entry From Git
  6. 2. Generate Entry From stdin/File Input
  7. 3. Update CHANGELOG.md
  8. 4. Compute the Next Version From Commits
  9. 5. Lint Commits Before Merge
  10. Conventional Commit Rules
  11. Script Interfaces
  12. Common Pitfalls
  13. Best Practices
  14. Hotfix Severity & SLAs
Ships with 9 files
  • 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
Commands it runs
python3 scripts/generate_changelog.py \
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
git log v1.3.0..HEAD --oneline | \
python3 scripts/version_bumper.py --current-version 1.3.0 --output-format json
python3 scripts/commit_linter.py --from-ref origin/main --to-ref HEAD --strict --format text
python3 scripts/commit_linter.py --input commits.txt --strict
cat commits.txt | python3 scripts/commit_linter.py --format json
More from claude-skills
All skills →
signup-flow-croWhen the user wants to optimize signup, registration, account creation, or trial activation flows.…Design & Presentationstrategic-alignmentCascades strategy from boardroom to individual contributor. Detects and fixes misalignment between…Otherprocess-mapperUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business…Design & Presentationsaas-scaffolderGenerates complete, production-ready SaaS project boilerplate including authentication, database…Securitysecrets-vault-managerUse when the user asks to set up secret management infrastructure, integrate HashiCorp Vault…Securityab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user…Testing & QA
About this skill
What does the changelog-generator skill do?

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

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill changelog-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.