skills.rest
ArabelaTso
ArabelaTsoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

change-log-generator

Generate Markdown changelogs from git commit history with conventional commits.

142|14|Updated Feb 14, 2026
Search Tags:#automation#git#changelog#conventional commits#commits#release notes
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill change-log-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-log-generator
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/change-log-generator
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill change-log-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of changelogs by analyzing git commits, patches, and pull requests, saving significant manual effort and ensuring consistency in release notes.

Core Features & Use Cases

  • Automated Commit Analysis: Parses git logs and commit messages, including conventional commits.
  • Categorization: Groups changes into predefined categories like Features, Bug Fixes, and Breaking Changes.
  • Markdown Generation: Formats the output into a clean, readable Markdown changelog.
  • Use Case: After a development sprint, use this Skill to automatically generate the CHANGELOG.md file for the upcoming release, ensuring all significant changes are documented accurately and efficiently.

Quick Start

Use the change-log-generator skill to create a changelog for the commits between the last tag and HEAD.

Frequently Asked Questions about change-log-generator

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

FAQPage Schema
How do I generate a changelog from git commit history?▼

To generate a changelog from git commit history, you need a tool that parses commit messages, diffs, and pull request data to automatically produce structured Markdown release notes. This Skill automates that exact parsing and categorization process.

Can I automatically categorize release notes using conventional commits?▼

Yes, you can categorize release notes using conventional commits. This Skill analyzes your commit messages and automatically groups changes into predefined categories like Features, Bug Fixes, and Breaking Changes for your changelog.

What is the best way to create a Markdown changelog after a development sprint?▼

The best way to create a Markdown changelog after a sprint is to automate generation by analyzing commits between your last tag and HEAD. This Skill formats the extracted commit data into a clean, readable Markdown file.

Does the changelog generator require any specific git branching model or dependencies?▼

No specific dependencies or branching models are required. The changelog generator works by analyzing your existing git log, commit messages, and pull request data directly from the repository history.

How do I document breaking changes in automated release notes?▼

To document breaking changes in automated release notes, the Skill parses your commit messages and patches to identify and categorize significant changes. It then groups these into a dedicated Breaking Changes section within the Markdown output.

Related Skills

Explore More Software Engineering Skills→
pantheon-orgpantheon-org
9

conventional-commits

Generate Git commit messages following the Conventional Commits specification.

Official
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

summarize-changes

Parse git diffs and commit logs into categorized Markdown reports.

Community
Intermediate
viktorbezdekviktorbezdek
10

git-workflow

Automate Git commit formatting, branch organization, and release note generation.

Community
Advanced