changelog-manager - SKILL.md Agent Skill

name: changelog-manager description: Manage CHANGELOG.md entries by appending new release sections. Use when a feature, fix, or change needs to be recorded in the changelog after implementation.

Changelog Manager

Append new entries to CHANGELOG.md — never rewrite prior history.

Format

Each release follows the template:

## <version> - <YYYY-MM-DD>

### Added
- <new features, tools, commands>

### Changed
- <behavior changes, refactors, renames>

### Fixed
- <bug fixes>

### Removed
- <deleted features, files>

### Notes
- <migration notes, caveats, context>

Use ## <version> - <YYYY-MM-DD> style headers. Use - N/A for empty sections.

Rules

Derive the next version from the latest CHANGELOG.md header (patch bump by default; minor for new public interfaces).
Never rewrite or delete prior entries — only append.
Use present tense, imperative style ("Add" not "Added feature X").
Reference file paths for changes (e.g. ads/beckhoff_client.py).
Keep descriptions brief — one line per entry.
Place the new section at the top of the file, above all existing entries.
After writing, verify: git diff CHANGELOG.md shows only the new section prepended.

Pre-commit must-run

Before any commit, check CHANGELOG.md for new changes not yet logged. If the commit adds/modifies behavior visible to a user (CLI, MCP tool, model, validation, docs) and there is no entry for it, update CHANGELOG first. This is not optional — skip only if the change is purely internal refactoring with zero user-facing impact.