changelog-generator

Topics in the source

• Changelog Generator
• Overview
• Core Capabilities
• When to Use
• Key Workflows
• 1. Generate Changelog Entry From Git
• 2. Generate Entry From stdin/File Input
• 3. Update CHANGELOG.md

Tier: POWERFUL Category: Engineering Domain: Release Management / Documentation Use this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control. Parse commit messages using Conventional Commit rules Detect semantic bump (major, minor, patch) from commit stream Render Keep a Changelog sections (Added, Changed, Fixed, etc.) Generate release entries from git ranges or provided commit input Enforce commit format with a dedicated linter script Support CI integration via machine-readable JSON output Before publishing a release tag During CI to generate release notes automatically During PR checks to block invalid commit message formats In monorepos where package changelogs require scoped filtering When converting raw git history into user-facing notes When the user has not decided the next version, derive it instead of guessing: Output JSON contains recommendedversion, bumptype (major/minor/patch/none), and with --include-commands the exact git tag commands. Feed recommendedversion into generatechangelog.py --next-version. Pre-

This is an excerpt. Refer to the complete source and its current requirements.