release-announce Skill

Manual fallback only. The version-bump-and-release.yml GitHub Action now handles version bumping and GitHub Release creation automatically at merge time. This skill is only needed if the Action fails or for manual re-announcements of existing versions.

Purpose: Generate a release announcement from CHANGELOG.md and create a GitHub Release. Discord notification is handled by the release-announce GitHub Actions workflow, triggered automatically when the release is published.

Step 1: Read Version and Changelog

1. Read the current version from plugins/soleur/.claude-plugin/plugin.json:

   Read plugins/soleur/.claude-plugin/plugin.json and extract the version field value.

2. Extract the ## [<version>] section from plugins/soleur/CHANGELOG.md. Parse from the ## [<version>] heading to the next ## [ heading (exclusive). If no matching section exists, error with "Changelog section for v<version> not found" and stop. Replace <version> with the actual version from step 1.

3. Generate a detailed summary of the extracted changelog section:

   • Include all categories present (Added, Changed, Fixed, Removed)
   • Tone: enthusiastic but professional
   • This summary is used as the GitHub Release body

Step 2: Create GitHub Release

1. Check if a release for this version already exists:

   gh release view "v<version>" 2>/dev/null
   

   Replace <version> with the actual version number (e.g., 2.32.1).

2. If the release already exists: warn "Release v<version> already exists, skipping" and stop.

3. Create the release:

   gh release create "v<version>" --title "v<version>" --notes "<full summary>"
   

4. If the command fails: warn with the error message.

5. Report results:

   • Print the GitHub Release URL if created
   • Note that Discord notification will be posted automatically by CI (requires DISCORD_WEBHOOK_URL repository secret)