changelog-generator

Generate user-facing changelogs from git commit history.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JuanJoseGonGi/skills --skill changelog-generator-juanjosegongi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/JuanJoseGonGi/skills/tree/main/changelog-generator
Command: npx skills add https://github.com/JuanJoseGonGi/skills --skill changelog-generator-juanjosegongi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of user-friendly changelogs and release notes directly from git commit history, streamlining the release process.

Core Features & Use Cases

  • Automated Changelog Generation: Analyzes git logs to create structured, human-readable release notes.
  • Commit Convention Support: Understands and leverages Conventional Commits for better organization.
  • Release Automation Integration: Provides guidance for tools like semantic-release and standard-version.
  • Use Case: Automatically generate release notes for your next software version by analyzing commits made since the last release, ensuring clear communication of new features and fixes to users.

Quick Start

Generate a changelog from commits since the last release.

Frequently Asked Questions about changelog-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 to analyze your commit logs and transform technical commit data into clear, human-readable release notes. This Skill automates that process by extracting updates since your last release to create customer-facing changelogs.

How do conventional commits help automate release notes?

Conventional commits help automate release notes by providing a standardized commit message structure that tools can easily parse. This Skill leverages that structure to organize technical commit data into clear, categorized updates for your software releases.

What is the best way to automate semantic versioning pipelines?

The best way to automate semantic versioning pipelines is to integrate tools like semantic-release and standard-version with your git workflow. This Skill provides guidance on configuring these tools to standardize release notes and automate version bumps.

Can I use this to create release notes from commits since the last release?

Yes, you can use this to create release notes from commits since the last release. It analyzes your git log to automatically generate structured, user-facing changelogs that communicate new features and fixes to your users.

Does this work with semantic-release and standard-version?

Yes, this works with semantic-release and standard-version by providing guidance for release automation integration. It helps standardize your release notes by configuring Conventional Commits and semantic versioning pipelines within these tools.