changelog-gen_skill

Overview

This skill generates markdown changelog entries from git history so you can produce release notes fast. It reads commits between two refs, groups them into standard categories, and outputs Keep a Changelog–style entries ready to add to CHANGELOG.md. One-command usage with minimal configuration makes it ideal for release workflows.

How this skill works

The tool collects git log between any two refs (tags, branches, commits) and normalizes commit messages. It sends the commit list to an AI parser which categorizes changes into Added, Changed, Fixed, Removed and cleans up terse or messy messages. The final output is formatted markdown that you can print to console or write directly to a file.

When to use it

• Preparing release notes for a new version
• Catching up a changelog you forgot to maintain
• Generating consistent changelogs across projects
• Creating GitHub release notes from a commit range
• Quickly turning commit history into human-friendly entries

Best practices

• Tag releases in git to define clear ranges
• Keep commit messages descriptive and focused
• Review AI-categorized output before publishing
• Run the tool as part of your release checklist or CI job
• Specify exact refs (tags or commits) to avoid missing changes

Example use cases

• Generate changelog between two tags: npx ai-changelog --from v1.0.0 --to v2.0.0
• Create notes from a tag to HEAD during release: npx ai-changelog --from v1.0.0 --to HEAD
• Write output directly to file: npx ai-changelog --from v1.0.0 --to v2.0.0 -o CHANGELOG.md
• Produce changelog for a specific commit range: npx ai-changelog --from abc123 --to def456
• Integrate in CI to auto-generate draft release notes on tag publish