skills.rest
Techlemariam
TechlemariamCOMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

Generate CHANGELOG.md from git history using conventional-changelog conventions.

Updated Aug 27, 2026
Search Tags:#automation#git#changelog#documentation#release-notes#conventional-commits
One-click install
npx skills add https://github.com/Techlemariam/IronForge --skill changelog-generator-techlemariam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Techlemariam/IronForge/tree/main/.agent/skills/changelog-generator
Command: npx skills add https://github.com/Techlemariam/IronForge --skill changelog-generator-techlemariam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog generation from git history based on conventional commits streamlines release communication and keeps documentation up-to-date.

Core Features & Use Cases

  • Auto-generate CHANGELOG.md from commit history using conventional-commits conventions.
  • Produce release notes with structured sections for features, fixes, docs, and other categories.
  • Use Case: teams can automatically generate accurate changelogs during release planning and documentation updates.

Quick Start

Run the tool to generate a CHANGELOG.md from your latest commits.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I auto-generate a changelog from git history using conventional commits?▼

To auto-generate a changelog from git history, this skill parses conventional commits to create a structured CHANGELOG.md. It organizes release notes into specific sections for features, fixes, and documentation.

What are conventional commits and how do they structure release notes?▼

Conventional commits are a standardized message format categorizing changes by type. This skill parses them from git history to generate release notes with distinct sections for features, fixes, and docs.

Do I need a specific git commit format to generate a CHANGELOG.md?▼

Yes, you need conventional commits in your repository history. The tool relies on these standardized commit messages to accurately parse features, fixes, and other categories for the changelog.

How do I create structured release notes for features and fixes during a release?▼

You create structured release notes by running this tool against your repository's git history. It extracts conventional commits and formats them into categorized sections within a CHANGELOG.md file.

What do I need to configure before generating a changelog from my repository?▼

Before generating a changelog, you need access to the repository's git history and a configured CHANGELOG target. The tool uses conventional commits to format the output documentation.

Related Skills

Explore More Software Engineering Skills→
lpjhelderlpjhelder

git-master

Create atomic Git commits with conventional formatting and manage repository history.

Community
Intermediate
zero-rehqzero-rehq

release-notes

Generate CHANGELOG.md and GitHub release notes from commits and worklog data.

Community
Advanced
bashfulrobotbashfulrobot

commit

Generate conventional Git commits with emojis, tags, and GitHub releases.

Community
Intermediate
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic