skills.rest
jholhewres
jholhewresCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog-gen

Generate CHANGELOG.md files by parsing Git conventional commits.

3|Updated Feb 13, 2026
Search Tags:#automation#git#changelog#documentation#conventional commits#release notes
One-click install
npx skills add https://github.com/jholhewres/devclaw-skills --skill changelog-gen-jholhewres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/jholhewres/devclaw-skills/tree/main/skills/changelog-gen
Command: npx skills add https://github.com/jholhewres/devclaw-skills --skill changelog-gen-jholhewres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of a CHANGELOG.md file by parsing Git commit history, specifically focusing on conventional commit messages.

Core Features & Use Cases

  • Automated Changelog Generation: Creates release notes directly from your Git commit history.
  • Conventional Commit Parsing: Understands and categorizes commits based on standard prefixes like feat:, fix:, etc.
  • Use Case: After merging a new feature and several bug fixes, use this skill to automatically update your CHANGELOG.md with a clear, organized list of changes for the next release.

Quick Start

Use the bash tool to list commits since the last tag.

Frequently Asked Questions about changelog-gen

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

FAQPage Schema
How do I generate a CHANGELOG.md from conventional commits?▼

You can generate a CHANGELOG.md from conventional commits by parsing Git history and categorizing entries based on commit prefixes like feat:, fix:, and perf: into organized release notes sections.

How do I organize Git release notes by commit type?▼

Organize Git release notes by parsing conventional commit prefixes, automatically sorting Git history into distinct sections like Features, Bug Fixes, and Performance improvements for your changelog.

Can I use Git tags for release boundary detection in changelog generation?▼

Yes, changelog generation supports integration with Git tags to identify release boundaries, grouping commits between tags into specific release versions and linking associated issues or pull requests.

Do I need a specific commit message format for automated changelog generation?▼

Automated changelog generation requires standard conventional commit message prefixes, such as feat: for features or fix: for bug fixes, to correctly parse and categorize your Git history into changelog sections.

What is the best way to automate release notes from Git history?▼

Automating release notes from Git history is best achieved by parsing conventional commit messages to automatically categorize features, bug fixes, and performance updates into a structured CHANGELOG.md file.

Related Skills

Explore More Software Engineering Skills→
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced
utkudarilmazutkudarilmaz
3

changelog

Generate CHANGELOG.md and release notes from git history.

Community
Intermediate
kirvinkirvin

release

Automate versioned software releases with semantic versioning and GitHub CLI.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate