pm-changelog

To generate a changelog from git history, this skill reads commit logs since the last tag and appends formatted entries to CHANGELOG.md. It groups changes by features, fixes, and breaking changes for software projects with frequent release cycles.

The best way to group git commits into release notes is by categorizing them into features, fixes, breaking changes, and other groups. This skill parses git logs and formats them into readable entries suitable for team documentation.

Yes, you can append generated changelog entries to an existing CHANGELOG.md file. If the file is missing, the skill creates it automatically and adds the formatted git commit history underneath.

This changelog generator works well with projects that have frequent release cycles and commits. It reads git logs since the last tag or entry and formats the changes into categorized release notes for team communication.

Breaking changes and features are separated by grouping commits into distinct categories when creating documentation from git logs. The skill reads the history and organizes entries into features, fixes, breaking changes, and other groups.