skills.rest
olivermorgan2
olivermorgan2COMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog

Parse git log history between two references to generate categorized markdown release notes.

Updated Apr 12, 2026
Search Tags:#automation#git#changelog#documentation#github#release
One-click install
npx skills add https://github.com/olivermorgan2/workflow-generator --skill changelog-olivermorgan2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/olivermorgan2/workflow-generator/tree/main/skills/changelog
Command: npx skills add https://github.com/olivermorgan2/workflow-generator --skill changelog-olivermorgan2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh.

What problem does it solve?

This skill automates the tedious process of parsing git history to create accurate, categorized release notes, ensuring your project documentation stays in sync with your actual development progress.

Core Features & Use Cases

  • Automated Categorization: Automatically groups commits into sections like Features, Fixes, and Docs based on conventional commit prefixes or GitHub PR labels.
  • Intelligent Deduplication: Merges near-identical commits and handles squash-merge patterns to keep your changelog clean and readable.
  • Use Case: When preparing for a new release, use this skill to instantly generate a markdown-formatted summary of all changes since the last tag, ready to be pasted into your CHANGELOG.md or a GitHub Release.

Quick Start

Use the changelog skill to generate release notes for all changes since the last git tag and output them to the console.

Frequently Asked Questions about changelog

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

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

Generate markdown release notes by parsing git log history between two references. The skill automatically categorizes commits into sections like Features and Fixes using conventional commit prefixes or GitHub PR labels.

Can I automate changelog creation from conventional commits and GitHub PR labels?▼

Yes, you can automate changelog creation by mapping conventional commit verbs and GitHub PR labels to structured categories. It intelligently deduplicates near-identical commits and handles squash-merge patterns for clean documentation.

Do I need the GitHub CLI to generate categorized release notes?▼

Yes, you need the GitHub CLI alongside git to generate categorized release notes. The GitHub CLI is required to resolve commit ranges and fetch pull request metadata for accurate automated categorization.

What is the best way to prepare a markdown summary for a GitHub Release?▼

The best way to prepare a markdown summary for a GitHub Release is to parse all changes since the last git tag. This generates a ready-to-use markdown summary of categorized features and fixes for your release workflow.

How does deduplication work when generating release notes from squash merges?▼

Deduplication during release note generation works by merging near-identical commits and resolving squash-merge patterns. This ensures your changelog remains clean and readable without redundant entries.

Related Skills

Explore More Software Engineering Skills→
webbotywebboty

qodo-pr-resolver

Fetch and resolve Qodo PR review issues for the current branch's open pull request.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
aakash-dharaakash-dhar

changelog

Generate release notes and changelogs from git history and pull requests.

Community
Advanced
sitharaj88sitharaj88
1

create-pr

Generate pull request titles, bodies, and test plans from staged changes.

Community
Intermediate