GravionLabs/elysion / .agents/skills/github-release
github-release
UnverifiedCut 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.
Owns the lifecycle of the rolling release/next branch (explicit release/<x.y> only in parallel lines). The model and the base-branch resolver are in the github-issue skill's references/release-branches.md. No dialogue, tool calls only; on Claude Code this runs in a forked context without the session history.
help (or --help, -h): print references/help.md unchanged, nothing else.
Prerequisites: gh authenticated, repo root, clean git status. Mode: cut [--feature <nr>] or finish [major] [--yes] [release/next|release/<x.y>]; finish takes optional release_review_notes (lines from the release review of deliver).
Check the state first
pwsh scripts/Get-ReleaseState.ps1 -Mode cut # or: -Mode finish [-Branch release/next]
The script is read-only and prints JSON: default, branch, state, openPrs, localAhead, staleLines, deleteAllowed, action, hasMajorCommit, releaseWorkflow, releasePr, defaultIsAncestor, mergeConflicts, releaseTest, olderReleaseTests, gate, warning. Exit 1 with a message on stderr (invalid branch name, no release branch) means stop and report. Do what action says; stop: ... means report the text and change nothing.
state | cut | finish |
|---|---|---|
absent | create | stop |
fresh (equals default) | no-op | stop: nothing to release |
unreleased | no-op | continue below |
behind (default moved on) | no-op | stop, merge default in first |
merged, released | recreate when deleteAllowed, else stop and name the blocker | merged with deleteAllowed: delete-branch; else stop "already released; cut a new release branch" |
released-continued | no-op | stop "already released; cut a new release branch" |
cut
action: create: createrelease/nextfrom the default branch and push it with upstream.action: recreate: deleterelease/nexton origin (git push origin --delete release/next; the guardrail allows exactly this), thengit checkout -B release/next origin/<default>and push with upstream. No force push, no+semvercommit.- Each
staleLinesentry was released and is never reused. Report it withgit push origin --delete release/<x.y>; the owner runs it (the guardrail blocks it in a session). Continue with the cut. releaseWorkflowfalse: tell the user the repo does not close issues at merge intorelease/*and offer to copytemplates/release-branch.ymlto.github/workflows/release-branch.yml(never silently, one PR per repo,references/closing.md).- With
--feature <nr>: insertRelease branch: release/nextas the second line of that issue's body (gh issue view <nr> --json body, thengh issue edit <nr> --body-file -), theParent ...line stays first.
finish
-
stateunreleased,openPrsempty: continue.defaultIsAncestorfalse (statebehind) stopsfinishbefore any release PR: reportmergeConflictsand the back-merge inreferences/back-merge.md;deliverstep 9 stops the same way. Otherwiseactionalready says stop; listopenPrswhen they block. -
Bump: no commit by default, on
release/nextand onrelease/<x.y>. GitVersion derives it from the Conventional Commits on the branch:fix:→ patch,feat:→ minor,<type>!:orBREAKING CHANGE:→ major; a release with only fixes is a patch release. Only the argumentmajor(deliberate escape hatch, e.g. batched renames; never ask in a fork) addsgit commit --allow-empty -m "chore: release major" -m "+semver: major"and a push, and only whenhasMajorCommitis false. -
releasePrset: CI keeps it current, report it. None: open it withgithub-pull-requestin release mode (branch,base_branch: <default>,title: release: <branch>,merged_prsper its default,feature_numberonly when recorded,release_review_noteswhen the caller passes them, plus the lineRC test open: <issue URL>whenreleaseTestis set,auto_merge: false). Never use a directgh pr create; whengithub-pull-requeststops, stop and report. Do not touchCHANGELOG.md: the release job onmainregenerates it with git-cliff, tags, publishes and closes the issues the release's PRs reference. Pass the milestone:Get-ReleaseState.ps1 -Mode finish -Milestone <name>. An openrelease-testissue setsreleaseTestandwarning(RC test open: <url>): print the warning, add the line to the release PR body. Withrelease.test.gate: truein.agents/config.jsonthe script returnsaction: stop: ...: report it, no release PR. -
Report the PR URL,
gh pr merge <nr> --merge(merge commit, never squash: a squash hides thefeat:/fix:commits from GitVersion and git-cliff) and the cleanupgit push origin --delete <branch>, then stop; never wait for the merge. The cleanup after the merge is a laterfinishon the merged branch:Get-ReleaseState.ps1returnsdelete-branchand that run deletesrelease/next. -
That later run, after the release PR is merged and the tag
v<x.y.z>exists, ends with the milestone hint instead of leaving the milestone open. Read the milestones once:pwsh ../github-milestone/scripts/Get-Milestones.ps1 -Mode list(read-only). The release routine is tag, thencreatethe next milestone (if missing), thenclose;--move-toneeds an existing open target, socreatecomes first:- An open
M<n>(the lowest, ascurrent):/github-milestone create(the next freeM<n+1>) first, then/github-milestone close M<n> --move-to M<n+1>(the version comes from the tag; the title becomesM<n> (x.y.z); without open issues a plainclose M<n>is enough). - Legacy, an open
x.y.zmilestone withtagged: true:createthe nextx.y.zmilestone first, then/github-milestone close <x.y.z> [--move-to <next>]. - Neither, or
github-milestonenot installed: no hint.
With
github-milestoneinstalledfinishdoes this itself (--yes: no question):scripts/Test-ReleaseVersion.ps1first (tag against the commits, a mismatch stops), then create, close unclosed PBIs ("Released in v<x.y.z>"),close --move-to, report with the next milestone's ready count. Steps:references/close-milestone.md. - An open
Gotchas
- Never merge the release PR yourself; the push to
mainbuilds, regenerates the changelog and closes the delivered issues. - Issues close at merge into
release/next:references/closing.md. A repo withoutcliff.tomlgets no changelog from CI:references/cliff-setup.md. - Hotfixes bypass this skill (
fix/<nr>-<slug>frommain, merge commit intomain); afterwards run the back-merge (references/back-merge.md: merge commit PR, never squash). - Workflows reference
GravionLabs/ciat the major tag@v<major>(today@v1, astemplates/release-branch.yml), never@mainor a commit SHA; third-party actions stay SHA-pinned where the repository requires it. - A release branch is never continued after its merge. The CI release PR title may show the branch name, not the version (
release-branches.md).
Report: mode, branch, PR URL (finish) or the Feature issue updated (cut).
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: 464k | 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: 196k | 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: 196k | 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: 196k | Updated | Claude CodeCodex | Verified | Install |