changelog-generator

Generate structured changelogs from git history and conventional commits.

4|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/aaaa47080/stock_agent --skill changelog-generator-aaaa47080
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/aaaa47080/stock_agent/tree/main/.opencode/skills/changelog-generator
Command: npx skills add https://github.com/aaaa47080/stock_agent --skill changelog-generator-aaaa47080

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of clean release notes by summarizing git history into structured changelogs, saving time and ensuring consistency across releases.

Core Features & Use Cases

  • Automated changelog generation: converts commits and PRs into organized release sections.
  • Conventional-commit aware: groups changes by feat, fix, docs, refactor, and chore for clear storytelling.
  • Use Case: Before tagging a release, generate a changelog from the latest commits to accompany the tag.

Quick Start

Run the changelog generator on your repository to produce a publishable release notes document.

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?

You can generate release notes from git history automatically by running a changelog generator that parses repository commits and PRs across branches and tags to produce structured, publishable release documentation.

Can I group commits by conventional commit types for my changelog?

Yes, conventional commits are parsed and grouped by categories such as feat, fix, docs, refactor, and chore, organizing your changelog into clear, structured sections for better storytelling.

How do I create a changelog before tagging a release?

To create a changelog before tagging a release, run the generator against your latest repository commits to automatically summarize the history into a formatted release notes document ready for publishing.

Does the changelog generator work with commits across multiple branches and tags?

Yes, the changelog generator processes repository history spanning multiple branches, tags, and pull requests, summarizing the collected data into organized changelog sections and optional stats.

What is the best way to turn PR descriptions into formatted changelog sections?

The best way to turn PR descriptions into formatted changelog sections is to use a conventional-commit aware generator that automatically extracts and categorizes pull request data into structured release notes.

Do I need a parser for conventional commits to generate structured release notes?

Yes, a parser for conventional commits is required to analyze your git history and accurately group changes into formatted sections based on commit types like feat, fix, and docs.