What problem does it solve?
Writing accurate Phoenix release notes requires manually reviewing commits, reading changed code, and updating multiple documentation files, which is slow and error-prone. This Skill automates the full workflow from identifying undocumented releases to publishing MDX pages.
Core Features & Use Cases
- Release Gap Detection: Compares GitHub releases against existing docs to find undocumented versions across all Phoenix packages (server, Python SDK, TypeScript SDK, evals, OTel).
- Code-Grounded Analysis: Reads actual changed files rather than relying on commit messages, classifying changes as user-facing or internal housekeeping.
- Multi-Touchpoint Publishing: Creates dated MDX files, updates the aggregate release-notes page, year overview cards, docs.json navigation, and optionally GitHub release descriptions.
- Use Case: After a week of Phoenix releases, ask the Skill to document them; it consolidates the changes into one well-organized release notes page with verified code examples and a Slack-ready summary.
Quick Start
Write release notes for all undocumented Phoenix releases since the last documented date.