skills.rest
rrbanda
rrbandaCOMMUNITY
Explore all skills by this author →
GitHub

wiki-changelog

Generate structured changelogs from git history grouped by time period and change type.

Updated Aug 23, 2026
Search Tags:#automation#git#changelog#versioning#commit-analysis
One-click install
npx skills add https://github.com/rrbanda/skills --skill wiki-changelog-rrbanda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-changelog
Source: https://github.com/rrbanda/skills/tree/main/skills/documentation/wiki-changelog
Command: npx skills add https://github.com/rrbanda/skills --skill wiki-changelog-rrbanda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes git commit history to produce structured changelogs categorized by change type, reducing manual effort and improving release transparency.

Core Features & Use Cases

  • Groups commits by time period (daily for recent activity, weekly for older history).
  • Classifies changes into Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), and Breaking changes (⚠️).
  • Outputs concise, publish-ready changelogs for release notes, dashboards, and documentation.

Quick Start

Run the changelog generator on your repository to produce a categorized changelog for the latest release.

Frequently Asked Questions about wiki-changelog

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

FAQPage Schema
How do I generate a structured changelog from git commit history?▼

To generate a changelog from git commit history, this Skill analyzes your repository and groups commits by time period, classifying each into Features, Fixes, Refactoring, Docs, Config, Dependencies, or Breaking changes to produce a publish-ready output.

Can I automatically categorize git commits by change type for release notes?▼

Yes, you can automatically categorize git commits for release notes. The Skill classifies each commit into distinct categories like Features, Fixes, and Breaking changes, then outputs a structured changelog ready for publication.

How does commit grouping by time period work for changelog generation?▼

Commit grouping by time period works by organizing recent activity daily for the last 7 days and switching to weekly grouping for older git history, creating a structured timeline for your generated changelog.

Does this changelog generator work with remote git repositories?▼

Yes, this changelog generator operates against both local and remote git repositories. It can optionally resolve a remote origin URL to link commits and changed files directly within the final structured changelog output.

What is the best way to automate release notes from git history?▼

The best way to automate release notes from git history is to run this Skill against your repository, which analyzes commits, classifies changes by type, and outputs a polished, categorized changelog without manual effort.

What do the different emoji classifications mean in automated git changelogs?▼

Emoji classifications in automated git changelogs represent change types: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), and Breaking changes (⚠️) to visually distinguish commit categories.

Related Skills

dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
korwlik23korwlik23

release-version

Coordinate SemVer version bumps, changelogs, annotated Git tags, and release notes.

Community
Advanced
jim60105jim60105
21

bump-version

Automate semantic version bumps, changelog generation, and Git tagging.

Community
Advanced
dudusoardudusoar

git-log

Generate Conventional Commits messages and update GIT_LOG.md documentation.

Community
Basic