What problem does it solve? Writing release changelogs by hand means manually reviewing every merged PR since the last release, categorizing each one, and figuring out who actually deserves credit — a process that is tedious and frequently misattributes work to whoever pressed merge rather than who wrote the code. ## Core Features & Use Cases - Automated release window enumeration: Builds the set of merged PRs from git reachability against the release ref, with pagination detection and exclusions for plumbing PRs, so no shipped work is silently omitted. - Emoji-driven categorized entries: Classifies each PR by labels or conventional-commit prefixes into sections like Features, Fixes, Security, and CI/CD, matching the repo's existing CHANGELOG.md format when one exists. - Supersede Credit Rule with verification: Resolves the true author through five detection paths (carry-forward templates, umbrella merges, free-text attribution) and verifies every credit against commit authorship, never crediting bots or AI agents. - PR delegation: Hands the finished entry to the om-auto-create-pr skill, which opens it as a docs-only PR with labels and a review pass. - Use Case: Before cutting release 0.4.11, run the skill to compile every PR merged since 0.4.10 into a formatted CHANGELOG.md entry with correct contributor credits, then review the resulting docs PR before merge. ## Quick Start Ask the agent to draft a changelog entry for the next release covering all PRs merged since the last release, optionally passing a version number or using --dry-run to preview the entry without changing any files.
