Aggregate git history and project docs into a Keep a Changelog formatted release log.
npx skills add https://github.com/doancan/mags --skill mags-changelog
Please help me install this Agent Skill. Skill: mags-changelog Source: https://github.com/doancan/mags/tree/main/skills/mags-changelog Command: npx skills add https://github.com/doancan/mags --skill mags-changelog
Changelog generation often requires manually curating entries from git history and project notes. This Skill automates that process, ensuring release logs are consistent and up-to-date.
Run mags_generate_changelog to create a changelog from the repository’s git history and project docs.
High-intent search queries and answers about installing and using this skill.
You can generate a changelog from git history by running the changelog generation command, which aggregates recent commits and project documentation into a structured release log formatted according to Keep a Changelog standards.
The Keep a Changelog format is a standardized convention for organizing release notes into categories like added, changed, and fixed. This Skill outputs your aggregated git history and project docs in this format for consistent release logs.
Yes, you can automate release log creation for any Git-tracked project. The Skill processes recent commits and updated documentation from any Git repository to produce a structured changelog without requiring manual curation.
Yes, this changelog generator works without external dependencies. It operates directly on any Git-tracked project to aggregate commit history and project docs into a Keep a Changelog formatted output.
To save generated changelogs to project docs, the Skill uses an internal document update function to write the aggregated release log directly to the docs/changelog path in your repository after processing git history.
The best way to summarize recent commits for a release is to aggregate git history and project docs automatically. This Skill surfaces added, changed, and fixed items from your repository history to enable quick release planning.
mir-amGenerate an initial CHANGELOG.md from repository metadata and commit history.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
douglasdennys45Generate project changelogs from Conventional Commits and Semantic Versioning.
trevorbyrumGenerate a changelog, bump version, draft release notes, and stage a git tag.
