ghe-changelog

Detect and categorize Git changes into structured CHANGELOG.md entries.

4|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Emasoft/ghe-marketplace --skill ghe-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghe-changelog
Source: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-changelog
Command: npx skills add https://github.com/Emasoft/ghe-marketplace --skill ghe-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill should be used when updating the project CHANGELOG, tracking requirement changes, recording design decisions, or documenting version history. Uses git-diff to detect and categorize changes to both code and requirements.

Core Features & Use Cases

  • Automated change detection: Diff-based categorization into Added/Changed/Fixed/Requirements
  • Changelog sections: Properly structured entries for code, design, and requirements
  • Traceability: Link changes to REQ updates and design decisions

Quick Start

Run after commits or on demand to generate organized changelog entries.

Frequently Asked Questions about ghe-changelog

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

FAQPage Schema
How do I automatically generate changelog entries from Git commits?

Changelog generation detects and categorizes code changes using git-diff to automatically organize entries into Added, Changed, Fixed, Requirements, and Design sections. This automation structures your CHANGELOG.md with categorized modifications from your Git history without manual sorting.

Can I track requirement changes alongside code changes in my changelog?

Yes. This Skill categorizes both code and requirement modifications, creating separate changelog sections for Requirements changes so design decisions and requirement updates are traceable and documented alongside code additions and fixes.

What does git-diff categorization mean for changelog management?

Git-diff analysis examines file modifications to classify changes into predefined categories—Added, Changed, Fixed, Requirements, and Design—creating organized, structured changelog entries that link code updates to their change type and intent.

Do I need to manually write changelog entries or does this automate the process?

This automates changelog entry generation by detecting Git-tracked changes and categorizing them automatically. You run it after commits to populate CHANGELOG.md with organized entries rather than writing each one manually.

What version control systems work with this changelog approach?

This Skill requires Git for version control. It uses git-diff to detect changes, so your project must use Git repositories to enable automated change detection and categorization for changelog generation.