release
release
Cuts a versioned release: pick the next semantic version, write proper release notes, tag the commit, and publish the GitHub release.
This sits next to /gh-bootstrap and /gh and answers a different question. /gh-bootstrap wires the release plumbing once (.github/release.yml, the tag-driven workflow). /gh is the raw gh release command reference. This skill is the ceremony you run each time you ship: decide the bump, draft the notes, tag, publish.
Where this skill fits
| Concern | Skill |
|---|---|
| One-time release-notes config + tag-driven workflow | /gh-bootstrap |
Raw per-command gh release create / view / upload |
/gh |
| Deciding the version, drafting notes, tagging, publishing | /release (this skill) |
| Local commit before any of this | /plate |
If the repo has a tag-driven release workflow (from /gh-bootstrap), pushing the tag is enough — the workflow publishes the release. This skill still decides the version and (optionally) drafts curated notes; it just stops after the tag push and reports that the workflow takes over. Otherwise it publishes the release itself with gh release create.