github-release-notes-writer

# GitHub Release Notes Writer Write Release Notes that help users understand why a release matters and how to upgrade safely without losing the exact changelog record. ## Operating Boundaries - Default to a local Markdown draft. Do not create, edit, publish, or delete a GitHub Release unless the user explicitly asks for that write. - Inspect release URLs, tags, pull requests, and repository content read-only when the user asks to research or draft. - Treat Release Notes as user- and upgrader-facing. Do not copy a reviewer-focused Release PR description unchanged. - Preserve the exact changelog baseline while curating its narrative and categories. - Prefer current code, tests, documentation, tags, and GitHub state over recalled conversation details. ## Workflow ### 1. Discover release conventions and inputs Read applicable repository instructions, release documentation, recent Release Notes, version manifests, and any user-provided baseline. Identify: - repository and target version - prerelease or stable status - immediate previous tag - target tag or immutable target commit - release branch when the target tag does not yet exist - last stable version of the previous major when preparing a stable major release - monorepo or multi-module upgrade requirements - requested output path and whether publication is authorized Follow the repository's established tone and heading style unless the user asks for another format. ### 2. Resolve the exact changelog range Use the ...