changelog

This skill analyzes commits on your feature branch compared to main and automatically creates categorized markdown files in the changelog/ directory. It reads commit messages to organize changes into conventional files like {PR_NUMBER}.added.md, {PR_NUMBER}.fixed.md, and {PR_NUMBER}.changed.md based on the type of change detected.

The skill parses conventional commit messages to categorize changes into standard changelog file types: added for new features, fixed for bug fixes, and changed for modifications. It generates predictable, machine-friendly markdown entries organized by PR number and change type in the changelog/ directory.

Yes, the skill integrates with standard Git workflows by comparing your feature branch to main and generating changelog files as part of your PR preparation. Simply provide the PR number as an argument, and it creates the appropriate markdown files in your changelog/ directory automatically.

The skill creates separate markdown files for each change type within your PR—one file for additions, one for fixes, one for modifications, and so on. Each file is named using the PR number and change category (e.g., 3519.added.md, 3519.fixed.md), keeping your changelog entries organized and predictable.

The skill writes changelog entries as markdown files stored in the changelog/ directory, using conventional naming with PR number and change type. This format is both human-readable and machine-friendly, making it easy to parse and aggregate entries when building release notes.