The problem
Long AI-assisted development sessions produce useful changes, but the reasoning and release impact can disappear into chat history. Changelog Generator makes documenting the finished work part of the delivery workflow.
Behavior
- Initializes a standard CHANGELOG when a project does not have one
- Categorizes work as Added, Changed, Deprecated, Removed, Fixed or Security
- Recommends major, minor or patch versions using Semantic Versioning
- Synchronizes versions across root and application package files
- Follows Keep a Changelog conventions
The project is intentionally small: version 1.0.0 contains the reusable skill instructions and installation documentation, but no executable scripts, fixtures or automated verification.
What the first version does not guarantee
The current instructions do not force the agent to inspect the real Git diff, compare tags or protect a dirty worktree before writing. They also assume that every package.json should share one version, which is not valid for every monorepo. A safer next version needs repository-state checks, explicit user approval before version edits, lockfile and non-Node manifest handling, structured output validation and tests. The source is public, but the repository has no LICENSE file, so this page does not describe it as MIT-licensed or open source.