skills.rest
webdevarif
webdevarifCOMMUNITY
Explore all skills by this author →
Website𝕏@webdevarifGitHub

changelog

Generate CHANGELOG.md entries from git history using conventional commit parsing.

Updated Apr 18, 2026
Search Tags:#automation#git#changelog#versioning#conventional commits#release notes#keep a changelog
One-click install
npx skills add https://github.com/webdevarif/claude-skills --skill changelog-webdevarif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/webdevarif/claude-skills/tree/main/changelog
Command: npx skills add https://github.com/webdevarif/claude-skills --skill changelog-webdevarif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing and maintaining a changelog is tedious and error-prone, especially when release notes must be compiled from dozens of commits. This Skill automates the process by reading git history and producing a structured CHANGELOG.md in Keep a Changelog format. ## Core Features & Use Cases - Conventional Commit Parsing: Categorizes commits into Added, Fixed, Changed, Removed, Security, and Documentation sections based on commit type prefixes like feat, fix, and refactor. - Incremental Updates: Detects existing CHANGELOG.md content and inserts only new entries above previous ones, never deleting existing history. - Flexible Ranges: Supports generating from the last tag, a specific tag range like v1.1.0..v1.2.0, or a full regeneration from all tags. - Use Case: Before cutting a release, run the Skill with the new version number to produce a dated, categorized release section with commit hashes for traceability. ## Quick Start Ask the AI to generate a changelog entry for version 1.2.0 from the commits since the last git tag.

Frequently Asked Questions about changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog from git commits automatically?▼

Run the changelog Skill to parse git log output and categorize commits by conventional commit type into Keep a Changelog sections. It fetches commits since the last tag or documented entry and writes grouped entries with short commit hashes into CHANGELOG.md.

How to create release notes for a specific version range?▼

Pass a tag range like v1.1.0..v1.2.0 as an argument to include only commits in that range. You can also pass a single version like v1.2.0 to label the new entry with that version and today's date.

Does the changelog generator work with non-conventional commits?▼

Yes, non-conventional commits are categorized by keywords such as remove, delete, vulnerability, or CVE, and fall into an Other category otherwise. The full commit message is used as the entry description when no type prefix exists.

Will updating CHANGELOG.md overwrite my existing entries?▼

No, the Skill never deletes or overwrites existing entries. New entries are inserted below the file header and above previous entries, preserving the full changelog history.

Why are merge commits missing from the generated changelog?▼

Merge commits are intentionally skipped because they add noise rather than meaningful change descriptions. Chore, ci, and build commits are also excluded unless they represent significant changes like a major dependency upgrade.

Related Skills

Explore More Software Engineering Skills→
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced
JansenAnalyticsJansenAnalytics
5

release-manager

Automate changelog generation, version bumps, and GitHub releases via CLI.

Community
Intermediate
Veloxia-agencyVeloxia-agency

changelog-generator

Generate markdown or JSON changelog entries from Conventional Commit histories.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced