changelog-automation

Generate release notes and changelogs from commits and PRs.

1|Updated Apr 14, 2026

Search Tags:#automation #git #changelog #generate #semantic-versioning #release-notes #conventional-commits

Ready to run

npx skills add https://github.com/Sumeet138/qwen-code-agents --skill changelog-automation-sumeet138

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill changelog-automation-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the generation of release notes and changelogs from commits, PRs, and releases, ensuring consistency with Keep a Changelog standards and reducing manual effort.

Core Features & Use Cases

Parse Conventional Commits and PR metadata to generate structured changelog entries.
Support semantic versioning and release-note formatting for GitHub/GitLab workflows.
Produce release notes templates and internal release notes for stakeholders.

Quick Start

Generate a changelog following Keep a Changelog for the latest release using the most recent commits and PR data.

Frequently Asked Questions about changelog-automation

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

FAQPage Schema

How do I generate changelogs from conventional commits automatically?▼

Changelog generation from conventional commits is automated by parsing commit and PR metadata to produce structured release notes. This ensures semantic versioning compliance and standardized changelog sections without manual input.

Can I format release notes for both GitHub and GitLab workflows?▼

Yes, release notes formatting supports both GitHub and GitLab environments. The automation applies Keep a Changelog standards to generate, format, and publish structured notes across both platforms.

What's the best way to maintain a Keep a Changelog standard across software releases?▼

Maintaining Keep a Changelog standards is best achieved by automating release notes generation from commits and PRs. This enforces consistent semantic versioning and structured sections for every release.

How does semantic versioning work with automated release notes?▼

Semantic versioning in automated release notes works by parsing conventional commit messages to determine version bumps. It categorizes changes into standardized changelog sections based on the commit type.

Do I need specific commit formats to automate changelog generation?▼

Yes, automating changelog generation requires using conventional commits. The automation parses the structured commit and PR metadata to determine semantic versioning and format the changelog entries accurately.

Why does my changelog automation fail to group commits into standardized sections?▼

Changelog automation fails to group commits when they do not follow conventional commit formatting. Proper metadata parsing requires strict adherence to conventional commits to map changes into standardized Keep a Changelog sections.