changelog

Name: changelog
Availability: InStock
Author: karimatayuta

Generate structured changelogs from git history with categorized release notes.

Updated Feb 7, 2026

Search Tags:#automation #git #changelog #documentation #release-notes #conventional-commits

Ready to run

npx skills add https://github.com/karimatayuta/graph-vector-rag --skill changelog-karimatayuta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/karimatayuta/graph-vector-rag/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/karimatayuta/graph-vector-rag --skill changelog-karimatayuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This changelog skill automates producing structured release notes by parsing git history and grouping changes into meaningful categories, reducing manual effort during releases.

Core Features & Use Cases

Automatic categorization of commits into Features, Bug Fixes, Documentation, and Chores.
Flexible scope: since last tag, between tags, or a custom range.
Output suitable for release notes, changelogs, or internal documentation.

Quick Start

Generate a changelog for the latest commits since the last tag.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I automatically generate release notes from git history?▼

Automatically generate release notes from git history by parsing commits and grouping them into structured categories like Features, Bug Fixes, and Documentation, which reduces manual effort during software releases.

Does this changelog generator work with conventional commits?▼

Yes, this changelog generator works with conventional commits or standard git metadata to parse history, categorize changes, and format the output into structured release notes for your repository.

How do I generate a changelog between two specific git tags?▼

To generate a changelog between two git tags, you can specify a custom range such as between tags, since the last tag, or a custom date window to parse the relevant commit history accurately.

What is the best way to categorize git commits for internal documentation?▼

The best way to categorize git commits for internal documentation is to automatically group parsed git history into Features, Bug Fixes, Documentation, and Chores to create formatted release notes suitable for team distribution.

Do I need any external dependencies to parse git history for changelogs?▼

No, you do not need external dependencies to parse git history for changelogs, as the process directly analyzes conventional commits or git metadata to output formatted release notes without requiring additional components.