changelog-generation

Generate Keep a Changelog format changelogs from git history and task records.

2|Updated Feb 4, 2026

Search Tags:#automation #git #changelog #developer tools #documentation #release notes

Ready to run

npx skills add https://github.com/PaulKinlan/docker-agent-test --skill changelog-generation-paulkinlan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generation
Source: https://github.com/PaulKinlan/docker-agent-test/tree/main/config/skills/writer/changelog-generation
Command: npx skills add https://github.com/PaulKinlan/docker-agent-test --skill changelog-generation-paulkinlan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of changelogs by analyzing git history, task records, or artifacts, transforming raw data into a user-friendly release note format.

Core Features & Use Cases

Automated Changelog Creation: Generates changelogs based on the "Keep a Changelog" format.
Data Source Integration: Can pull change data from git commits, task boards, or artifact repositories.
Categorization: Automatically categorizes changes into Added, Changed, Fixed, Removed, and Security.
User-Centric Rewriting: Transforms developer-focused commit messages into user-facing descriptions.
Use Case: After a development sprint, use this Skill to automatically generate the release notes for the new version by analyzing the git log since the last release.

Quick Start

Use the changelog-generation skill to create a changelog for the 'Unreleased' version using git history from the last 7 days.

Frequently Asked Questions about changelog-generation

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 by analyzing git history and transforming raw commit data into a user-friendly format. This Skill automates that process, categorizing changes into Added, Changed, Fixed, Removed, and Security sections.

What's the best way to format git commit messages for release notes?▼

Formatting release notes involves rewriting developer-focused commit messages into user-centric descriptions. This Skill transforms raw git log data into the standardized Keep a Changelog format for your release notes.

Do I need jq and bash to generate changelogs from git?▼

Yes, you need jq, git, and bash to generate changelogs using this Skill. These dependencies are required for data processing and artifact registration when analyzing git history.

Can I pull changelog data from task records and artifacts instead of git?▼

Yes, you can pull change data from task boards or artifact repositories instead of git. This Skill supports data source integration to automate changelog creation from these alternative inputs.

How does the Keep a Changelog format categorize changes?▼

The Keep a Changelog format categorizes changes into Added, Changed, Fixed, Removed, and Security. This Skill automatically sorts your git history into these specific categories for clear release notes.

How do I create release notes after a development sprint?▼

To create release notes after a sprint, analyze the git log since the last release. This Skill generates the changelog for the new version by processing recent commit history automatically.