github-releaseslisted

# GitHub Releases Language-agnostic release workflow for GitHub projects. ## Use cases This skill covers three release tasks — identify which one the user wants: 1. **Cut or publish a release** (default) — run the Prerequisites and Workflow below. 2. **Set up or update `docs/RELEASING.md`** — the project's release guide. Follow [setup-modify-release-workflow.md](references/setup-modify-release-workflow.md) instead of the release workflow. 3. **Set up release CI** — automate the mechanical *publish* half of a release in a CI pipeline. This is design guidance only; it does not write provider-specific pipeline files. Follow [ci-pipeline-guide.md](references/ci-pipeline-guide.md). The Prerequisites and Workflow below apply to use case 1. ## Prerequisites (Phase 1) Before starting, verify: - `command -v gh` succeeds (GitHub CLI installed) - `gh auth status` succeeds (GitHub CLI authenticated) - `git status --porcelain` returns empty (clean working tree) - You are on the default branch — releases are cut from the default branch — and in sync with its remote Run the checks as [release-workflow.md — Phase 1](references/release-workflow.md) specifies; it owns the `DEFAULT_BRANCH` derivation. If `gh` is missing or unauthenticated, or any check fails, stop and guide the user through fixing it — see [troubleshooting.md](references/troubleshooting.md). Do not start the workflow with a failed prerequisite. ## Workflow **1. Read the project release guide** Check for `docs/RELEASI