Skip to content

GravionLabs/elysion / .agents/skills/github-release

github-release

Unverified

Cut 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.

statecutfinish
absentcreatestop
fresh (equals default)no-opstop: nothing to release
unreleasedno-opcontinue below
behind (default moved on)no-opstop, merge default in first
merged, releasedrecreate when deleteAllowed, else stop and name the blockermerged with deleteAllowed: delete-branch; else stop "already released; cut a new release branch"
released-continuedno-opstop "already released; cut a new release branch"

cut

  1. action: create: create release/next from the default branch and push it with upstream.
  2. action: recreate: delete release/next on origin (git push origin --delete release/next; the guardrail allows exactly this), then git checkout -B release/next origin/<default> and push with upstream. No force push, no +semver commit.
  3. Each staleLines entry was released and is never reused. Report it with git push origin --delete release/<x.y>; the owner runs it (the guardrail blocks it in a session). Continue with the cut.
  4. releaseWorkflow false: tell the user the repo does not close issues at merge into release/* and offer to copy templates/release-branch.yml to .github/workflows/release-branch.yml (never silently, one PR per repo, references/closing.md).
  5. With --feature <nr>: insert Release branch: release/next as the second line of that issue's body (gh issue view <nr> --json body, then gh issue edit <nr> --body-file -), the Parent ... line stays first.

finish

  1. state unreleased, openPrs empty: continue. defaultIsAncestor false (state behind) stops finish before any release PR: report mergeConflicts and the back-merge in references/back-merge.md; deliver step 9 stops the same way. Otherwise action already says stop; list openPrs when they block.

  2. Bump: no commit by default, on release/next and on release/<x.y>. GitVersion derives it from the Conventional Commits on the branch: fix: → patch, feat: → minor, <type>!: or BREAKING CHANGE: → major; a release with only fixes is a patch release. Only the argument major (deliberate escape hatch, e.g. batched renames; never ask in a fork) adds git commit --allow-empty -m "chore: release major" -m "+semver: major" and a push, and only when hasMajorCommit is false.

  3. releasePr set: CI keeps it current, report it. None: open it with github-pull-request in release mode (branch, base_branch: <default>, title: release: <branch>, merged_prs per its default, feature_number only when recorded, release_review_notes when the caller passes them, plus the line RC test open: <issue URL> when releaseTest is set, auto_merge: false). Never use a direct gh pr create; when github-pull-request stops, stop and report. Do not touch CHANGELOG.md: the release job on main regenerates 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 open release-test issue sets releaseTest and warning (RC test open: <url>): print the warning, add the line to the release PR body. With release.test.gate: true in .agents/config.json the script returns action: stop: ...: report it, no release PR.

  4. Report the PR URL, gh pr merge <nr> --merge (merge commit, never squash: a squash hides the feat:/fix: commits from GitVersion and git-cliff) and the cleanup git push origin --delete <branch>, then stop; never wait for the merge. The cleanup after the merge is a later finish on the merged branch: Get-ReleaseState.ps1 returns delete-branch and that run deletes release/next.

  5. 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, then create the next milestone (if missing), then close; --move-to needs an existing open target, so create comes first:

    • An open M<n> (the lowest, as current): /github-milestone create (the next free M<n+1>) first, then /github-milestone close M<n> --move-to M<n+1> (the version comes from the tag; the title becomes M<n> (x.y.z); without open issues a plain close M<n> is enough).
    • Legacy, an open x.y.z milestone with tagged: true: create the next x.y.z milestone first, then /github-milestone close <x.y.z> [--move-to <next>].
    • Neither, or github-milestone not installed: no hint.

    With github-milestone installed finish does this itself (--yes: no question): scripts/Test-ReleaseVersion.ps1 first (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.

Gotchas

  • Never merge the release PR yourself; the push to main builds, regenerates the changelog and closes the delivered issues.
  • Issues close at merge into release/next: references/closing.md. A repo without cliff.toml gets no changelog from CI: references/cliff-setup.md.
  • Hotfixes bypass this skill (fix/<nr>-<slug> from main, merge commit into main); afterwards run the back-merge (references/back-merge.md: merge commit PR, never squash).
  • Workflows reference GravionLabs/ci at the major tag @v<major> (today @v1, as templates/release-branch.yml), never @main or 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).

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: 464kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexUnverifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall