skills.rest
jubscodes
jubscodesCOMMUNITY
Explore all skills by this author →
GitHub

gspdev-changelog

Update CHANGELOG.md from git history following Keep a Changelog format.

49|4|Updated Feb 20, 2026
Search Tags:#automation#git#changelog#versioning#release#keepachangelog
One-click install
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gspdev-changelog
Source: https://github.com/jubscodes/get-shit-pretty/tree/main/dev/skills/gspdev-changelog
Command: npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often forget to keep the CHANGELOG.md up to date and properly formatted, leading to missing user‑facing change information and inconsistent release notes.

Core Features & Use Cases

  • Update Unreleased: Scans recent git commits and populates the [Unreleased] section following Keep a Changelog conventions.
  • Release Promotion: Converts the [Unreleased] section into a versioned entry using the current VERSION file.
  • Full Rebuild: Regenerates the entire changelog from git history, ensuring consistency after major refactors.

Quick Start

Run the gspdev-changelog skill in update mode to automatically refresh the CHANGELOG.md.

Frequently Asked Questions about gspdev-changelog

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

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

To update an Unreleased changelog section, the skill scans recent git commits and automatically populates the file following Keep a Changelog formatting conventions.

How do I promote unreleased changelog entries to a versioned release?▼

To promote unreleased changelog entries to a versioned release, the skill reads the current VERSION file and converts the Unreleased section into a versioned entry.

What do I need to maintain a Keep a Changelog formatted file from git commits?▼

Maintaining a Keep a Changelog formatted file from git commits requires access to the git repository, a VERSION file, and standard Unix tools such as git, grep, and bash.

When should I do a full rebuild of my CHANGELOG.md?▼

A full rebuild of your CHANGELOG.md should be done after major refactors to regenerate the entire changelog from git history and ensure formatting consistency.

Does standard Unix tooling work for automating release notes from a VERSION file?▼

Yes, standard Unix tooling works for automating release notes by using bash, git, and grep alongside a VERSION file to process commits and maintain the changelog.

Related Skills

Explore More Software Engineering Skills→
zrongzrong
11

git-commit

Format git commit messages, stage atomic changes, and generate CalVer tags.

Community
Advanced
Priivacy-aiPriivacy-ai
1.5k

release

Automate spec-kitty-cli releases to PyPI with version bumps and changelog updates.

Official
Advanced
Greenmamba29Greenmamba29

changelog-generator

Generate structured CHANGELOG.md entries from git commit history and semantic versioning tags.

Community
Intermediate
sunny0826sunny0826
3

release-notes

Categorize Git commit logs into structured release notes in Markdown.

Community
Intermediate