What problem does it solve? Writing accurate, user-facing release notes for a calendar-versioned project requires manually reconciling commits, changesets, merged PRs, and beta soak state, which is error-prone and easy to get wrong. ## Core Features & Use Cases - Stable Range Resolution: Computes the changelog range from the last stable tag to the beta source commit, never from master HEAD, so post-beta commits are excluded. - Breaking Change Detection: Scans migrations, schema diffs, API routes, and commit messages for breaking changes and requires an upgrade path for each. - Structured Changelog Output: Produces a categorized markdown file (Breaking Changes, Highlights, Improvements, Fixes, Upgrade Guide, Contributors) with inline PR and contributor attribution. - Release Case Upsert: Optionally upserts a release Case via the Todero API and writes the changelog body as a document revision. - Use Case: A maintainer promoting a soaked beta to stable asks the agent to draft the release notes; the skill checks idempotency, gathers inputs, writes releases/beta/v{version}.md at full stable depth, and presents it for sign-off. ## Quick Start Generate the stable changelog for the upcoming Todero release by reading commits and changesets since the last stable tag.
