Generate changelog entries in Keep a Changelog format from Git history.
npx skills add https://github.com/686f6c61/alfred-dev --skill changelog-686f6c61
Please help me install this Agent Skill. Skill: changelog Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/documentacion/changelog Command: npx skills add https://github.com/686f6c61/alfred-dev --skill changelog-686f6c61
This Skill automates the creation of changelog entries, ensuring consistency and adherence to the Keep a Changelog standard, making it easier for users to understand what has changed between software versions.
CHANGELOG.md entry for the new release, ensuring all new features and bug fixes are clearly documented for end-users.Use the changelog skill to draft a new entry for a fixed bug related to user login.
High-intent search queries and answers about installing and using this skill.
To generate a changelog from Git history, this Skill analyzes your commit messages and semantic versioning tags to classify modifications into standard Keep a Changelog categories like Added, Changed, Fixed, and Security for your release notes.
The Keep a Changelog format is a standardized documentation structure that categorizes software modifications into Added, Changed, Removed, Fixed, and Security sections to make release notes clear and understandable for end-users.
You document bug fixes and new features in a CHANGELOG.md file by drafting user-oriented descriptions of modifications and organizing them under standardized version headers and categories following the Keep a Changelog standard.
Yes, understanding issue tracking data is required to accurately classify and describe modifications, allowing the generated changelog entries to include proper context and links to issues or pull requests.
The best way to automate release notes creation after a sprint is using a tool that categorizes modifications into standardized groups and drafts user-oriented language, ensuring all new features and bug fixes are clearly documented.
Your release notes lack consistency because they do not adhere to a standardized format; applying the Keep a Changelog standard structurally categorizes security updates and fixed bugs into distinct, predictable sections.
plurigridGenerate user-facing changelogs from git commit history.
utkudarilmazGenerate CHANGELOG.md and release notes from git history.
bjcoombsGenerate pull requests, sync findings to issue trackers, and emit CI gate workflows.
involvexGenerate changelogs and release notes from conventional commits.