changelog-generator

Transforms git commit history into structured, categorized release notes.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Haseeb-Arshad/TaskHive --skill changelog-generator-haseeb-arshad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Haseeb-Arshad/TaskHive/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/Haseeb-Arshad/TaskHive --skill changelog-generator-haseeb-arshad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the heavy lifting of turning raw git commits into clear, customer-friendly release notes, saving time and reducing manual toil during releases.

Core Features & Use Cases

  • Automated history analysis: Scans commits over a specific time period or between versions to capture changes.
  • Smart categorization: Groups changes into features, improvements, fixes, breaking changes, and security.
  • User-friendly translation: Converts technical commits into language suitable for customers and stakeholders.
  • Professional formatting: Generates clean, structured changelog entries that fit brand guidelines.
  • Noise filtering: Excludes internal commits (refactors, tests) from customer-facing notes.

Quick Start

Run the changelog generator from your project repository to produce release notes from the latest commits since the last version.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate release notes from git commit history automatically?

To generate release notes from git commit history, this Skill scans your repository's commits over a specific time period or between versions, categorizes them, and formats them into structured customer-facing updates. It automates the transformation of raw commits into professional release notes.

Can I filter out internal refactoring and test commits from customer-facing changelogs?

Yes, you can filter out internal commits from customer-facing changelogs. The Skill implements noise filtering to automatically exclude internal commits such as refactors and tests, ensuring only relevant changes appear in your structured release notes.

How are git commits categorized when creating user-facing release notes?

When creating user-facing release notes, git commits are categorized into distinct groups: features, improvements, fixes, breaking changes, and security. This smart categorization organizes raw commit history into structured, easy-to-read sections.

What is the best way to turn technical git commits into language suitable for stakeholders?

The best way to turn technical git commits into stakeholder-friendly language is through user-friendly translation. This Skill converts technical commit messages into clear language suitable for customers and stakeholders while generating clean, structured changelog entries.

Does the changelog generator work for weekly summaries and app store updates?

Yes, the changelog generator works for weekly summaries and app store updates. It is designed to produce release notes, weekly summaries, or store and app updates across any repository by scanning and categorizing commit history.

Do I need any specific dependencies to convert git commits into structured changelogs?

No specific dependencies are required to convert git commits into structured changelogs. The Skill operates independently with no external dependencies, allowing you to run it directly from your project repository to generate release notes.