Update CHANGELOG.md from git history following Keep a Changelog format.
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-changelog
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
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.
Run the gspdev-changelog skill in update mode to automatically refresh the CHANGELOG.md.
High-intent search queries and answers about installing and using this skill.
To update an Unreleased changelog section, the skill scans recent git commits and automatically populates the file following Keep a Changelog formatting conventions.
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.
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.
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.
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.
zrongFormat git commit messages, stage atomic changes, and generate CalVer tags.
Priivacy-aiAutomate spec-kitty-cli releases to PyPI with version bumps and changelog updates.
Greenmamba29Generate structured CHANGELOG.md entries from git commit history and semantic versioning tags.
sunny0826Categorize Git commit logs into structured release notes in Markdown.
