What problem does it solve? Writing accurate release notes requires manually reviewing every merged PR and commit between versions, which is error-prone and time-consuming, especially when notes must be published in both Chinese and English. ## Core Features & Use Cases - Evidence Collection: Runs a bundled Node.js script to gather merged pull requests, uncovered first-parent commits, and contributor GitHub usernames for a given release range. - Bilingual Note Drafting: Produces mirrored Chinese and English release notes grouped into Features, Improvements, Fixes, and Resolved Issues, with evidence links and author credits for every bullet. - Draft Release Writing: Writes the notes directly to a Draft GitHub Release via the gh CLI after verifying the tag, workflow status, and assets, with a read-only dry-run mode for review. - Use Case: After the v* release workflow finishes, ask the agent to prepare the release; it resolves the base..target range, collects PR and commit evidence, drafts bilingual notes, and fills the Draft GitHub Release for your approval. ## Quick Start Use the release skill to prepare bilingual release notes for the latest tag and show them for review before updating the Draft GitHub Release.