git-changelog

Generate structured Markdown changelogs from Git commit history between two refs.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/xiaoli123/agentscope-core --skill git-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-changelog
Source: https://github.com/xiaoli123/agentscope-core/tree/main/agentscope-core/src/test/resources/e2e-skills/git-changelog
Command: npx skills add https://github.com/xiaoli123/agentscope-core --skill git-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Converts Git commit history into structured changelogs and release notes, reducing manual drafting effort during releases.

Core Features & Use Cases

  • Group commits by type (feat, fix, docs, chore, etc.) into labeled sections like Features, Bug Fixes, and Chores.
  • Support specifying a range with from/to refs and optional output file, producing a Markdown changelog with a summary header.
  • Useful for release planning, governance, and stakeholder communication across any Git-based project.

Quick Start

Run the script to generate a grouped Markdown changelog from git history between two refs and save it to CHANGELOG.md.

Frequently Asked Questions about git-changelog

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

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

Generate markdown release notes from git commit history by running a script that parses commits between two refs and groups them into structured sections. It produces a formatted changelog file reducing manual drafting effort.

How do I group git commits by type for a changelog?

Group git commits by type for a changelog by parsing conventional commit messages like feat, fix, and docs. The tool automatically categorizes these into labeled sections such as Features, Bug Fixes, and Chores.

Can I generate a changelog between two specific git refs?

Yes, you can generate a changelog between two specific git refs by specifying from and to references in the script. It processes the commit history within that range and outputs a markdown file with a summary header.

What is the best way to automate release notes from conventional commits?

The best way to automate release notes from conventional commits is using a script that reads git history, applies conventional commit types, and formats a markdown changelog. This streamlines release planning and stakeholder communication.

Does this changelog generator work for any git-based project?

Yes, this changelog generator works for any git-based project needing a summarized view of changes. It applies conventional commit grouping to produce markdown release notes suitable for governance and documentation.