Generate Git Changelogs from Commit History
Generates structured changelogs from git history, grouped by time period and classified by change type.
Why it matters
Automate the creation of user-friendly changelogs by analyzing your Git commit history. This skill transforms raw commit data into structured, concise release notes, highlighting key changes and breaking updates.
Outcomes
What it gets done
Analyze Git commit logs, including messages, authors, and dates.
Group commits by time period (daily/weekly) for readability.
Classify commits into categories like Features, Fixes, and Breaking Changes.
Generate concise, project-specific descriptions for changelog entries.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-wiki-changelog | bash Overview
Wiki Changelog
Generates structured changelogs from git history: commits grouped by time period, classified by type (features, fixes, refactoring, docs, config, dependencies, breaking), written in project terminology. Use when asked what changed recently, to generate a changelog, summarize commits, or review recent development activity.
What it does
This skill generates structured, user-facing changelogs directly from git history rather than raw commit dumps. Its procedure: examine the git log (commits, dates, authors, messages), group entries by time period - daily buckets for the last 7 days, weekly buckets for anything older - classify each commit into one of seven categories (Features, Fixes, Refactoring, Docs, Config, Dependencies, Breaking), and generate concise descriptions in the project's own terminology rather than generic commit-message paraphrasing.
Its constraints keep the output focused and readable: it prioritizes user-facing changes over internal implementation detail, merges related commits into a single coherent description rather than listing each one separately, pulls terminology from the project's own README so descriptions match how the team already talks about the product, and highlights breaking changes prominently with migration notes rather than burying them alongside routine fixes.
When to use - and when NOT to
Use this skill when someone asks what changed recently, wants a changelog generated, wants commits summarized, or wants to understand recent development activity at a glance rather than scrolling raw git log output.
It is specifically a git-history summarization tool - it's not a substitute for a proper release-notes process requiring product or marketing sign-off, though it can serve as a solid first draft for one.
Inputs and outputs
Input is a repository's git history over some time range. Output is a structured changelog organized by time period (daily for the last week, weekly further back), with each entry classified by change type (feature, fix, refactor, docs, config, dependency, or breaking change), written in the project's own terminology, and with breaking changes called out with migration guidance.
Integrations
Reads directly from git log (commits, dates, authors, messages) and cross-references the project's README for terminology consistency.
Who it's for
Developers or maintainers who want a quick, structured summary of recent development activity - for release notes, team updates, or catching up after time away - rather than manually reading through raw commit history.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.