changelog-generator

Generates changelogs from Git history, commit messages, and pull requests.

90|10|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/korallis/Droidz --skill changelog-generator-korallis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/korallis/Droidz/tree/main/droidz_installer/payloads/droid_cli/default/skills/changelog-generator
Command: npx skills add https://github.com/korallis/Droidz --skill changelog-generator-korallis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive changelogs by parsing Git history, commit messages, and pull requests, streamlining the release documentation process.

Core Features & Use Cases

  • Automated Changelog Generation: Creates detailed release notes from commit data.
  • Categorization: Helps categorize changes into features, fixes, and breaking changes.
  • Use Case: When preparing for a new software release, use this Skill to automatically generate the release notes based on all commits made since the last version.

Quick Start

Use the changelog-generator skill to create a changelog from the last release tag to the current commit.

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 history automatically?

Generate release notes from Git history automatically by parsing commit messages and pull requests from your last release tag to the current commit. This categorizes changes into features, fixes, and breaking changes for comprehensive release documentation.

Can I create a changelog from conventional commits?

Yes, you can create a changelog from conventional commits. The generation process adheres to the Conventional Commits standard, categorizing your structured commit messages into distinct features, fixes, and breaking changes for documentation.

What is the best way to categorize Git commits for release documentation?

The best way to categorize Git commits for release documentation is to automate the parsing of commit messages and pull requests. This process automatically groups changes into features, fixes, and breaking changes to streamline documentation.

Does this changelog generator work with pull request data?

Yes, this changelog generator works with pull request data. It parses both Git history and pull requests to extract changes, ensuring your release notes comprehensively cover all modifications made since the last software release.

How do I prepare a changelog for a new software release?

Prepare a changelog for a new software release by generating release notes from all commits made since the last version tag. This automates the categorization of features and fixes, streamlining the release documentation process.

Do I need any external dependencies to automate changelog updates?

No, you do not need any external dependencies to automate changelog updates. The generation process operates independently to parse Git history and commit messages without requiring additional packages or external libraries.