changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill changelog-automation-drgaciw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/drgaciw/academic-compliance-hub-glm/tree/main/agents/plugins/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill changelog-automation-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of changelogs and release notes, ensuring consistency and saving significant developer time.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelogs based on commit messages following Conventional Commits.
  • Release Note Standardization: Adheres to the Keep a Changelog format for clear and structured release notes.
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically generate release notes for each new version, summarizing all changes since the last release.

Quick Start

Use the changelog-automation skill to generate a changelog from your git commits.

Frequently Asked Questions about changelog-automation

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

FAQPage Schema
How do I automate changelog generation from conventional commits?

Automate changelog generation by parsing git commit messages that follow the Conventional Commits standard to produce structured release notes. This Skill uses tools like conventional-changelog to summarize changes since the last release automatically.

What is the best way to standardize release notes for semantic versioning?

Standardize release notes for semantic versioning by adhering to the Keep a Changelog format and parsing Conventional Commits. This ensures clear, structured release notes that align with semantic versioning industry standards.

Can I use semantic-release to generate release notes in a CI/CD pipeline?

Yes, you can integrate this Skill into your CI/CD pipeline using semantic-release to automatically generate release notes for each new version. It summarizes all changes since the last release based on commit message conventions.

Does standard-version work with Conventional Commits to manage changelogs?

Yes, standard-version works with Conventional Commits to automate changelog creation and semantic versioning. This Skill supports standard-version as one of the tools for comprehensive release automation and changelog management.

How do I set up a release process using commit message conventions?

Set up a release process by standardizing your commit message formats using Conventional Commits and integrating a tool like conventional-changelog. This automates semantic versioning and generates your changelog without manual intervention.

When do I need Conventional Commits for changelog automation?

You need Conventional Commits for changelog automation when you want to automatically generate structured release notes from your git history. This standard allows tools to parse features, fixes, and breaking changes to determine semantic versioning bumps.