hos-gh-release-note

Provide the tag and the Skill diffs it against the previous tag found via git tag --sort=v:refname. It drafts a body with What's Changed sections and a compare link, shows it for confirmation, then sends it with gh release create or gh release edit.

A new major leads with Kicked Out, Deprecated, and New Features; other releases lead with Security. Bug Fixes, Requirements, Supply Chain, Dependencies, and CI follow when they have content, and empty sections are omitted entirely.

Yes. If gh is missing or not authenticated, the Skill says which is the case and stops at producing the release note text. The note's structure, ordering, and language are identical whether it is sent or pasted by hand.

Each package.json field gets its own table with columns for package name, old version, new version, semver step, and note. Rows sort Major to Patch, additions and removals have an empty semver cell, and overrides get a third table with resolved versions.

Yes, via gh release edit with --notes-file, without dropping the release to draft. The current body is saved to a file first because GitHub keeps no history of replaced release bodies.

Every release created by the Skill uses gh release create --draft because deciding readiness to publish is a human judgement. The draft flag is only removed when explicitly requested, using gh release edit --draft=false.