writing-release
Guides how work reaches main (the default release branch) and becomes a release in a GitHub-hosted repository. Covers choosing an integration lane (reviewed PR, self-merge PR or direct push), writing pull-request titles and bodies that become merge commits, setting up CI-driven releases with tooling derived from what the repository contains, deciding whether a prerelease channel is warranted, and recovering from missing or failed releases. Use when opening, titling or landing a pull request to main, deciding whether a change needs a PR, setting up a release pipeline or CI release job, choosing release tooling, investigating "why didn't it release" or a failed release job, adding a prerelease, dev or rc channel, or when asked to "cut a release". Not for writing commit messages or rebasing topic branches, which belong to the writing-history skill.
