Changelog Generator

Purpose

Generate structured, human-readable changelogs and release notes from conventional commit history, GitHub release data, or JIRA release versions. Automated changelogs reduce manual release effort, enforce consistent formatting, and provide clear communication to users and stakeholders.

Agent Protocol

Trigger

Exact user phrases: "generate changelog", "release notes", "conventional changelog", "CHANGELOG.md", "auto-changelog", "git-cliff", "standard-version", "release-please", "semantic-release", "generate release notes".

Input Context

• Commit message convention (Conventional Commits, Angular convention, custom)
• Output format (Keep a Changelog, custom Markdown, GitHub release, Slack message)
• Tool preference (git-cliff, standard-version, release-please, semantic-release, auto-changelog)
• Source of truth (git log, GitHub releases, JIRA)
• Release cadence (continuous delivery, scheduled releases, hotfixes)
• Versioning strategy (semver, calver, date-based, custom)
• Monorepo structure (single changelog vs per-package)