Update CHANGELOG.md with dated entries when a git version tag is created.
npx skills add https://github.com/kodexArg/gdt-syv --skill kdx-agent-changelog
Please help me install this Agent Skill. Skill: kdx-agent-changelog Source: https://github.com/kodexArg/gdt-syv/tree/main/skills/kdx-agent-changelog Command: npx skills add https://github.com/kodexArg/gdt-syv --skill kdx-agent-changelog
This Skill prevents missed release notes by ensuring CHANGELOG.md is updated exactly when a new git version tag is created, instead of relying on manual updates or ambiguous triggers.
Ask the agent to record the release by mentioning the git tag you created, e.g., "tag v1.2.0".
High-intent search queries and answers about installing and using this skill.
To auto-update CHANGELOG.md when creating a git version tag, you need a tool that reads git logs between the previous tag and HEAD, summarizes commits into categories, and appends a dated entry. This automation triggers specifically upon explicit git tag creation.
Generating release notes from git tags is best handled by summarizing the commit history between the previous version tag and HEAD. This process categorizes changes into Added, Changed, Fixed, Removed, and Setup sections for concise documentation.
Changelog automation does not work without explicitly creating a git tag. The system is designed to trigger only when a user explicitly mentions creating or applying a git version tag, preventing ambiguous updates and ensuring accurate release documentation.
To summarize git commits between two tags for release documentation, the tool inspects the git log for the specific tag range. It then appends concise, one-line-per-change bullets under controlled categories directly into your existing CHANGELOG.md file.
You can use predefined changelog categories when documenting version releases, specifically Added, Changed, Fixed, Removed, and Setup. The automation formats entries strictly under these allowed scopes to maintain controlled formatting.
The release notes automation modifies only the CHANGELOG.md file in your repository. It inserts a new dated entry near the top of the document while preserving the existing content and structure of your release documentation.
RebelliousSmileGenerate and update CHANGELOG.md from Git commit history with version tags.
rust-worksMaintain CHANGELOG.md entries in Keep a Changelog format.
PlagueHOUpdate CHANGELOG.md and create a release tag from commits since the last version tag.
li3pGenerate human-readable changelog entries from git history and diffs.
