Gh release

Skill K95M65/AI_ONBOARD/skills/gh-release

Cut a GitHub release with the gh CLI, using changelog or auto-generated notes. Use when tagging and publishing a release. Pairs with the changelog skill.From its SKILL.md

Install

npx -y skills add K95M65/AI_ONBOARD --skill gh-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.1 KB, 248 tokens by cl100k_base, as published. Nobody here has run it

GitHub release

Steps

Assemble notes with the changelog skill (save to RELEASE-NOTES.md), or let GitHub generate them.
Create the tag + release:
```
gh release create v<x.y.z> --title "v<x.y.z>" --notes-file RELEASE-NOTES.md
```
- Auto notes instead: --generate-notes.
- Pre-release: --prerelease. Draft: --draft.
- Attach build artifacts: gh release create v<x.y.z> ./dist/* --notes-file RELEASE-NOTES.md.
Verify: gh release view v<x.y.z> --web.

Versioning (SemVer)

major — breaking changes (the changelog breaking section drives this).
minor — new features, backward-compatible.
patch — fixes only.

Notes

Tag the intended commit — releases are awkward to unpublish cleanly.
Never move or reuse a published tag; cut a new patch instead.
Releasing from CI: gh uses GITHUB_TOKEN; ensure it has contents: write.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.