Generate Keep a Changelog compliant release notes from git history.
npx skills add https://github.com/vecear/Nipponverb --skill changelog-writer-vecear
Please help me install this Agent Skill. Skill: changelog-writer Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/changelog-writer Command: npx skills add https://github.com/vecear/Nipponverb --skill changelog-writer-vecear
Automates the generation of changelogs and release notes from git history, PR titles, and issue references to ensure consistent, production-ready documentation.
Run the tool against your repository with the previous release tag to generate a formatted changelog and release notes.
High-intent search queries and answers about installing and using this skill.
You can generate release notes by analyzing git commit history since your previous release tag. This Skill parses commit messages, PR titles, and issue references to automatically categorize changes and format structured Keep a Changelog compliant release documentation.
Semantic versioning bumps are suggested by analyzing categorized git commits. The tool identifies breaking changes for major bumps, new features for minor bumps, and fixes for patch bumps, applying semantic versioning rules directly to your release notes generation process.
Yes, you can format your changelog to follow the Keep a Changelog standard. The tool parses your git commits and automatically structures them into standard sections like Added, Changed, Fixed, and Removed to ensure consistent, production-ready release documentation.
You can identify breaking changes by parsing git commit messages and PR titles for specific flags or footers. The tool surfaces these breaking changes prominently in the generated changelog and suggests a major semantic version bump accordingly.
The best way to automate changelog generation is using a tool that parses commit messages, categorizes them by type like feat or fix, and outputs Keep a Changelog compliant documentation. This ensures consistent release notes without manual formatting.
Yes, you need a previous git tag to generate a structured changelog. The tool analyzes the commit history since the last release tag to accurately categorize new changes, suggest semantic version bumps, and format the release notes.
micaelmaltaStandardize Git commit messages using Conventional Commits rules.
sunholo-dataAutomates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.
saleorConfigure GitHub Actions workflows for automated tests, builds, and releases.
allanninalConvert git commits into changelogs following Keep a Changelog and Conventional Commits.
