Skip to content

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

github-release

Verified

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.

references/closing.md

View on GitHub
# Closing issues at merge

`Closes #n` fires only on the default branch, so an issue whose PR merges into `release/*` would stay open until the release. The rule instead: an issue closes when its PR is merged into `release/next` (or `release/<x.y>`). "Released" is a closed issue in a closed milestone (`github-milestone close`), not an open issue with a label.

## Lifecycle

1. A PR merges into a `release/*` branch. The reusable workflow `GravionLabs/ci/.github/workflows/release-branch.yml@v1` (`release-branch.yml` template) closes every issue the PR closes or references (`Closes`/`Fixes`/`Refs #n` in the PR body or its commits) with the comment "ships with <milestone>" (`none` without milestone), and closes the parent PBI and Feature once all their children are closed. Only merged PRs whose base is the pushed branch count.
2. `close-release-issues` (`gh-release`) is the safety net: when the release lands on `main` it closes what is still open (issues with `Closes #n`, their open sub-issues, parents whose sub-issues are all closed). An Epic is never closed this way.
3. `github-release finish` after the tag closes the milestone itself (`references/close-milestone.md`).

## A reverted PR

The workflow never reopens. If a merged PR is reverted, reopen its issues by hand (`gh issue reopen <nr>`) and comment why.

## One-time catch-up

Issues labelled `merged` from the old label lifecycle are still open. Run the workflow once with `workflow_dispatch` (Actions, "Release branch", branch `release/next`); set `dry-run` first to see which issues it would close. Afterwards the label is no longer used.

## Rollout to existing repos

One PR per repo: copy `templates/release-branch.yml` to `.github/workflows/release-branch.yml` (replace an inline copy of the workflow; set the input project-url) and open the PR with `github-pull-request`. `cut` offers this when no workflow in `.github/workflows/` calls `release-branch.yml` of GravionLabs/ci.

## Permissions

- Token requirements are in the README of GravionLabs/ci (`release-branch.yml`): a classic PAT with scopes `repo` and `workflow` (and `project`).
- The workflow needs `contents: read`, `issues: write`, `pull-requests: write` (the calling job grants them to the reusable workflow, `permissions: {}` at the top).
- Secrets are passed explicitly (`GH_PAT` required, `PROJECT_TOKEN` optional), not `secrets: inherit`. Without `GH_PAT` the workflow falls back to `github.token`: a PAT is needed so PRs created by CI trigger the required checks; closing works with `github.token`.
- The project Needs sync needs a classic PAT with scope `project` in secret `PROJECT_TOKEN`, else `GH_PAT`. A fine-grained token does not work for a user-owned project (only an organization-owned project accepts one). Failures per issue are warnings and never fail the job.

## Known limit

The release PR step of the reusable `release-branch.yml` (`versioning/release-pr`) accepts only `release/<x.y>` and ignores `release/next` (GravionLabs/ci#55). Closing is a separate step and is not affected. Checked 2026-10-26: GravionLabs/ci#55 is OPEN (current state: `gh issue view 55 -R GravionLabs/ci --json state`).
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: 471kUpdated 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: 198kUpdated 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: 198kUpdated 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: 198kUpdated Claude CodeCodexVerifiedInstall