Generate Professional Changelogs from Git History

The Changelog Generator is an autonomous agent that analyzes git repositories and produces professional, well-structured changelogs communicating changes to developers and users. It works in five stages: first analyzing the repository via Bash git log commands to extract commit history, version tags, and release branches, and using Glob to locate existing changelog files, package.json, or version files; then categorizing commits by parsing conventional commit patterns (feat:, fix:, docs:) with Grep to identify breaking changes, deprecations, and security fixes, filtering out merge commits and trivial changes; then detecting version information from git tags following semantic versioning, including pre-release versions (alpha, beta, rc) and release dates from tag timestamps; then enhancing content by transforming technical commit messages into user-friendly descriptions, adding migration guidance for breaking changes, and including issue/PR links; and finally validating chronological ordering and formatting consistency across version ranges.

Use this agent when a repository's commit history needs to become a genuinely user-facing changelog rather than a raw commit log - it writes for end users, not just developers, and requires migration steps for every breaking change rather than just flagging that something broke. It recognizes specific conventional-commit patterns to auto-categorize entries: feat: maps to Added, fix: to Fixed, docs: to Documentation, and both a BREAKING CHANGE: footer and a bang suffix on the commit type map to Breaking Changes. It is not meant to run blind when git history isn't accessible - its own guideline is to request repository access or manual version input rather than guess at what changed, and it prioritizes security fixes in their own dedicated section with CVE numbers where available rather than burying them in a generic Fixed list.

### Changelog

All notable changes to this project will be documented in this file.

### [Unreleased]

### Added
- New feature descriptions

### Changed
- Modified functionality

### Deprecated
- Soon-to-be removed features

### Removed
- Deleted features

### Fixed
- Bug fixes

### Security
- Security improvements

### [1.2.0] - 2024-01-15

### Added
- Feature X with improved performance
- New API endpoint for Y functionality

### Fixed
- Critical bug in Z component (#123)

Given a git repository, the agent produces a changelog in standard Keep a Changelog format like the one above, organized into Added, Changed, Deprecated, Removed, Fixed, and Security sections per version, in reverse chronological order with issue/PR references linked and breaking changes marked prominently with migration guidance attached.

Maintainers and release managers who want a changelog generated directly from commit history rather than written from memory after the fact, especially on projects that already follow conventional commit conventions the agent can parse automatically. It suits teams that need every breaking change to carry migration guidance and every security fix surfaced in its own section, and that want the agent's categorization rationale stated explicitly rather than a changelog handed over as an unexplained black box.