jikime-workflow-changelog

You can automatically generate a changelog by parsing Git commit history into structured release notes. This Skill transforms raw commits into user-friendly summaries, categorizing them based on the Conventional Commits specification.

Yes, the changelog generator fully supports Conventional Commits and Keep a Changelog standards. It parses commit messages according to these specifications to ensure release notes are properly structured and consistently categorized.

To detect breaking changes in release notes, the Skill automatically scans and identifies them from your Git commit history. It highlights these breaking changes explicitly in the generated changelog to alert users of potential migration requirements.

Yes, you can output changelogs in JSON format for CI/CD pipeline integration. The Skill supports multiple output formats including Markdown and JSON, allowing seamless integration with various automated Git workflows and release management systems.

The best way to automate release notes creation is converting Git commits into categorized release summaries. This Skill automates the process, transforming raw commit history into user-friendly changelog entries for each upcoming release.

To categorize bug fixes and features in a changelog, the Skill parses Conventional Commits metadata from your Git history. It automatically groups commits into distinct categories like features and fixes, ensuring clarity for users.