GravionLabs/elysion / .agents/skills/github-release
github-release
VerifiedCut the rolling release/next branch or finish it with the release PR and changelog. Use for "cut a release", "finish the release" or when no release branch exists.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| references/back-merge.md | markdown | 911 B |
| references/cliff-setup.md | markdown | 1.5 KB |
| references/close-milestone.md | markdown | 1.9 KB |
| references/closing.md | markdown | 3.1 KB |
| references/help.md | markdown | 3.3 KB |
| scripts/Get-ReleaseState.ps1 | script | 11.6 KB |
| scripts/Test-ReleaseVersion.ps1 | script | 2.5 KB |
| templates/cliff.toml | config | 1.3 KB |
| templates/release-branch.yml | config | 1.1 KB |
references/help.md
View on GitHub# /github-release
## Usage
```
/github-release cut [--feature <nr>]
/github-release finish [major] [release/next|release/<x.y>]
/github-release help
```
Cuts the rolling `release/next` branch, or finishes it with the release PR into the default branch.
## Arguments and flags
- `cut`: creates `release/next` from the default branch when absent, recreates it after a release (only when deletion is allowed), reports stale `release/<x.y>` lines; offers the `release-branch.yml` caller workflow when the repo has none.
- `--feature <nr>`: with `cut`, records `Release branch: release/next` as the second line of that Feature issue.
- `finish`: opens (or reports) the release PR with `github-pull-request` in release mode; once merged, a later `finish` deletes the branch.
- Milestone hint: once the release PR is merged and tagged `v<x.y.z>`, the later `finish` points to `/github-milestone close M<n>` (version from the tag, the title becomes `M<n> (x.y.z)`) and `/github-milestone create` for the next `M<n+1>`; with open issues left, `create` first, then `close M<n> --move-to M<n+1>`. Legacy repositories with an open `x.y.z` milestone get `/github-milestone close <x.y.z> [--move-to <next>]` and `create` of the next `x.y.z`.
- `--yes`: with `finish` after the merge, closes the milestone without asking: version check (`pwsh scripts/Test-ReleaseVersion.ps1 -Tag v<x.y.z>`, a mismatch stops), create the next `M<n+1>`, close unclosed PBIs with "Released in v<x.y.z>", `close --move-to`. Without it one confirmation lists the moved issues. Steps: `references/close-milestone.md`.
- `major`: with `finish`, adds one empty commit with `+semver: major` (not again when one exists).
- `release/next` or `release/<x.y>`: the branch to finish; default is the current release branch, else `release/next` on origin.
- Read-only state checks, JSON on stdout: `pwsh scripts/Get-ReleaseState.ps1 -Mode cut|finish|base [-Branch <b>] [-Issue <nr>]`. `cut` and `finish` report `state`, `openPrs`, `action` (`stop: ...` means change nothing); `base` resolves the integration branch.
- Version bump: no commit by default. GitVersion derives it from Conventional Commits: `fix:` patch, `feat:` minor (a `+semver: minor` commit message is GitVersion's directive for the same bump; the skill itself only ever adds `+semver: major`), `!:` or `BREAKING CHANGE:` major.
- RC test: `finish` with an open `release-test` issue in the milestone (`-Milestone <name>`) adds `RC test open: <issue URL>` to the release PR body and warns; with `release.test.gate: true` in `.agents/config.json` it refuses until the issue is closed.
- Human gate: the release PR is never merged by the skill. You merge it with a merge commit (`gh pr merge <nr> --merge`, never squash); the push to `main` builds, tags and closes the delivered issues.
- Changelog: git-cliff, generated by the release job on `main`, never edited by the skill. A repo without `cliff.toml` gets none; setup in `references/cliff-setup.md`.
## Examples
- `/github-release cut`
- `/github-release cut --feature 42`
- `/github-release finish`
- `/github-release finish major`
- `/github-release finish release/1.4`
## Config
none
## See also
- `references/cliff-setup.md`, `references/closing.md`
- `github-issue` (`references/release-branches.md`), `github-pull-request`, `github-milestone`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |