changelog-automation

Generate Keep a Changelog-compliant release notes from conventional commits and PRs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tctibbs/agent-workflows --skill changelog-automation-tctibbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/tctibbs/agent-workflows/tree/main/claude/general/documentation/skills/changelog-automation
Command: npx skills add https://github.com/tctibbs/agent-workflows --skill changelog-automation-tctibbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the creation of release notes and changelogs from commits, PRs, and version milestones.

Core Features & Use Cases

  • Generate release notes from conventional commits and PRs.
  • Produce Keep a Changelog-compliant changelogs with semantic versioning.
  • Release notes templates for GitHub/GitLab and automation hooks.
  • Use Case: Automatically generate release notes for a new version by aggregating merged PRs and commit messages.

Quick Start

Generate a changelog for the upcoming release by aggregating recent commits and PRs.

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?

Automating changelog generation from conventional commits involves parsing commit messages and merged PRs to produce structured, Keep a Changelog-compliant release notes with semantic versioning for GitHub or GitLab projects.

Can I generate Keep a Changelog-compliant release notes for GitHub and GitLab?

Yes, you can generate Keep a Changelog-compliant release notes for GitHub and GitLab by aggregating version milestones and conventional commits into structured sections using standard release notes templates and automation hooks.

What's the best way to aggregate merged PRs into semantic-versioning release notes?

The best way to aggregate merged PRs into semantic-versioning release notes is to parse conventional commit messages from project milestones and automatically generate structured changelog sections formatted for standard export.

Does automated changelog generation require standard commit message formats?

Automated changelog generation requires conventional commit message formats to accurately parse commit history and categorize changes into structured semantic-versioning sections within the Keep a Changelog-compliant output.

How do conventional commits map to structured sections in a changelog?

Conventional commits map to structured changelog sections by parsing commit message prefixes to categorize changes automatically, generating Keep a Changelog-compliant release notes grouped by semantic-versioning milestones.