changelog

Generate markdown changelogs from git history using conventional commit types.

Updated Feb 13, 2026

Search Tags:#automation #git #changelog #developer tools #conventional commits #release notes

Ready to run

npx skills add https://github.com/g-zenr/relay-api --skill changelog-g-zenr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/g-zenr/relay-api --skill changelog-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of changelogs by parsing git commit history, saving developers time and ensuring consistent release notes.

Core Features & Use Cases

Automated Changelog Generation: Creates changelogs based on git logs and conventional commit standards.
Categorization: Groups changes into 'Added', 'Changed', 'Fixed', and 'Security' sections.
Use Case: After a development sprint, use this Skill to generate a changelog entry for the upcoming release, summarizing all new features, bug fixes, and significant changes.

Quick Start

Generate a changelog for the latest release using the changelog skill.

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 history automatically?▼

You can generate a changelog from git history between specific tags or since the last tag. This Skill parses conventional commit types and formats the output into markdown with distinct sections for Added, Changed, Fixed, and Security updates.

How do conventional commits map to release notes sections?▼

Conventional commits map to release notes sections by categorizing git history into Added, Changed, Fixed, and Security updates. This automated parsing ensures consistent release notes formatting directly from your commit messages.

Can I generate a changelog between two specific git tags?▼

Yes, you can generate a changelog between specific git tags or since the last tag. The Skill parses the commit history within that range and formats the categorized changes into a markdown changelog.

Do I need conventional commit formatting to use this changelog generator?▼

Yes, conventional commit formatting is required because the changelog generator categorizes commits based on conventional commit types. This standard allows it to accurately group changes into Added, Changed, Fixed, and Security sections.

What is the best way to summarize a development sprint for a release?▼

The best way to summarize a development sprint for a release is using an automated changelog generator. It parses your git history to summarize new features, bug fixes, and significant changes into a formatted markdown changelog.