Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Install GreptimeDB Release Runbook
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GreptimeTeam/greptimedb greptimedb-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/greptimedb-release .claude/skills/greptimedb-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .claude/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GreptimeTeam/greptimedb greptimedb-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/greptimedb-release .agents/skills/greptimedb-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .agents/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GreptimeTeam/greptimedb greptimedb-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/greptimedb-release .cursor/skills/greptimedb-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .cursor/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GreptimeTeam/greptimedb.git --path .agents/skills/greptimedb-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GreptimeTeam/greptimedb greptimedb-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/greptimedb-release .gemini/skills/greptimedb-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .gemini/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GreptimeTeam/greptimedb greptimedb-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/greptimedb-release .github/skills/greptimedb-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .github/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GreptimeTeam/greptimedb greptimedb-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GreptimeTeam/greptimedb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/greptimedb-release .opencode/skills/greptimedb-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "greptimedb-release" agent skill from https://github.com/GreptimeTeam/greptimedb/tree/main/.agents/skills/greptimedb-release into .opencode/skills/greptimedb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "greptimedb-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
greptimedb-release- GitHub stars
- 6.7k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 630 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
- Works in 7 steps: Inputs: version and branch → Verify the Cargo version → Generate and curate the changelog → …
- Publishing a new GreptimeDB minor or major release
- SKILL.md covers Prerequisites & remote, 0. Inputs: version and branch, 1. Verify the Cargo version and 2. Generate and curate the…, plus 5 more sections
- Calls git and gh
What it does
Every step runs against the `GreptimeTeam/greptimedb` repository, and the agent asks you for the version and, if needed, the branch. The branch follows from the version: for example v1.1.0 lives on `release/v1.1`, a new minor or major is cut from `main` (with an offer to create the release branch, with your consent), and a patch release uses the existing release branch that carries cherry-picked commits.
Before anything is published, the workspace version in `Cargo.toml` on the release branch must match the version being released, read from a freshly fetched `FETCH_HEAD` rather than a possibly stale remote-tracking ref. Creating the release creates the tag and starts CI, so the agent confirms with you before that outward-facing step. Changelog writing is delegated to the separate `greptimedb-release-note` skill.
When your agent uses it
- Publishing a new GreptimeDB minor or major release
- Cutting a patch release from an existing release branch
- Checking that the Cargo version matches before tagging
Example prompts
- “Release GreptimeDB v1.1.0 from main.”
- “Publish the v1.0.3 patch on the release/v1.0 branch.”
- “Check the Cargo workspace version on the release branch before we tag.”
Requirements
- GitHub CLI `gh`, authenticated
- `git`
- `git cliff` and Python, for changelog generation through the release-note skill
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 28ec3ff. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GreptimeDB Release Runbook loads about 1.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 630 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from GreptimeTeam/greptimedb at commit 28ec3ff, republished under its Apache-2.0 licence (© GreptimeTeam). 630 words, ~1,439 tokens.
Download SKILL.mdSave it as
.claude/skills/greptimedb-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- greptimedb-release
- description
- Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
GreptimeDB Release Runbook
Publish a formal GreptimeDB release on GreptimeTeam/greptimedb. Always operate against
that repo (for gh, pass --repo GreptimeTeam/greptimedb). Changelog generation is a
separate, involved task — use the greptimedb-release-note skill for it.
This whole flow touches public infrastructure. Confirm with the user before the outward-facing step (creating the release, which creates the tag and triggers CI).
Prerequisites & remote
- Tools:
gh(check withgh auth status) andgit. Changelog generation additionally needsgit cliffand Python — see thegreptimedb-release-noteskill. - Resolve the remote first. This runbook writes
<remote>for the git remote pointing atGreptimeTeam/greptimedb; substitute your actual name (oftenupstream, sometimesoriginon a direct clone):git remote -v | grep -i 'GreptimeTeam/greptimedb' | awk '{print $1}' | head -1
0. Inputs: version and branch
- Ask the user for the version to release (e.g.
1.1.0,1.0.3) and, if needed, the branch. - Branch is inferred from version:
MAJOR.MINOR→release/v<MAJOR>.<MINOR>.v1.0.0 / v1.0.1 / v1.0.2live onrelease/v1.0;v1.1.0lives onrelease/v1.1.- Infer it, then double-check with the user.
- New minor/major (
X.Y.0) is cut frommain. Ifrelease/vX.Ydoes not exist on the remote, offer to create it from the intendedmaincommit (with the user's consent):git push <remote> <commit>:refs/heads/release/vX.Y. - Patch (
X.Y.Z, Z>0) must use the existingrelease/vX.Ybranch (it carries cherry-picked commits). - Check what exists on the remote:
git ls-remote --heads <remote> 'release/*'.
1. Verify the Cargo version
The workspace version on the release branch must equal the version being released, or
stop. Fetch the branch first, then read FETCH_HEAD directly — git fetch <remote> release/vX.Y only opportunistically updates the remote-tracking ref
<remote>/release/vX.Y (and only when the remote has a matching configured refspec), so it
may be missing or stale (e.g. a custom <remote>, or a branch just created in §0). Reading
FETCH_HEAD always reflects the tip just fetched:
git fetch <remote> release/vX.Y
git show FETCH_HEAD:Cargo.toml | grep -A30 '\[workspace.package\]' | grep -m1 version(For a fresh minor cut from main, <remote>/main and release/vX.Y are usually the same
commit.)
2. Generate and curate the changelog
Use the greptimedb-release-note skill. It produces CHANGELOG-vX.Y.Z.md (uncommitted)
and the docs-blog variant. Review the highlights with the user and iterate before
publishing.
3. Create the GitHub release (creates the tag + triggers CI)
Do NOT pre-create the tag. Creating the release creates the tag and fires the
tag-push CI (.github/workflows/release.yml) that builds all binaries (~hours).
Confirm with the user, then:
gh release create vX.Y.Z \
--repo GreptimeTeam/greptimedb \
--target release/vX.Y \
--title "Release vX.Y.Z" \
--notes-file CHANGELOG-vX.Y.Z.md \
--prerelease- Title convention:
Release vX.Y.Z. - Always create as
--prerelease: prerelease here is just a "build in progress" marker. The CI clears it on success (see §5). (The user creating it on the web works too.) - Verify:
gh release view vX.Y.Z --repo GreptimeTeam/greptimedb --json name,tagName,isPrerelease,draft,targetCommitish.
Show full SKILL.md (224 more words)Show less
4. Open the docs release-note PR (do not wait for CI)
Right after triggering the release, open the docs draft PR (see the docs section of the
greptimedb-release-note skill). It only needs the finalized changelog.
Then delete the local CHANGELOG-vX.Y.Z.md (its content now lives in the release body
and the docs blog post).
5. After the CI build finishes (~hours)
CI's publish-github-release action, for a tag matching ^vX.Y.Z$, runs
ncipollo/release-action with allowUpdates: true, prerelease=false,
makeLatest=true, omitBody=true (so it keeps our changelog body but finalizes the
flags). These flags are described from the current .github/workflows/release.yml —
verify against the workflow if behavior differs. Verify success:
gh release view vX.Y.Z --repo GreptimeTeam/greptimedb --json isPrerelease,assetsLatest handling is conditional on whether this is the newest version:
- Releasing the latest version (e.g. v1.1.0 when nothing newer exists) → CI's finalized state (non-prerelease, latest) is correct; do nothing.
- Releasing a non-latest line (e.g. a patch
v1.0.3whilev1.1.0is already latest) → set it back to non-latest after CI finishes:gh release edit vX.Y.Z --repo GreptimeTeam/greptimedb --latest=false.
6. Rollback (only on failure, with double confirmation)
Show the user exactly what will be removed first; never delete blindly.
gh release delete vX.Y.Z --repo GreptimeTeam/greptimedb # remove the release
git push <remote> :refs/tags/vX.Y.Z # remove the tagConventions / gotchas
- Remotes:
<remote>is whatever points atGreptimeTeam/greptimedb(see Prerequisites).ghdefaults can be unreliable in a repo with many remotes — always pass--repo GreptimeTeam/greptimedb. - Release title is always
Release vX.Y.Z. - When reasoning about "previous version", skip nightly / build-suffixed tags
(
*-nightly-*,vX.Y.Z-rc.N-<sha>-<date>-*).
© GreptimeTeam, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/greptimedb-release of GreptimeTeam/greptimedb.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 28ec3ff
Compare with similar skills
GreptimeDB Release Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GreptimeDB Release Runbook this skillGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Hunk Release Workflowmodem-dev/hunk | 9.6k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 9.2k | — | ~7.5k | Automated safety check: Pass | Custom licence | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 53k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
Codex Proxy RS Release
zyycn/codex-proxy-rs
Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.
More from GreptimeTeam/greptimedb
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
GreptimeDB Release Notes
GreptimeTeam/greptimedb
Generates a GreptimeDB release changelog with git cliff, subtracts patch PRs already shipped, rebuilds contributors and prepares the docs-repo blog PR.
Related
Categories
Questions about GreptimeDB Release Runbook
What does GreptimeDB Release Runbook do?
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR. Every step runs against the `GreptimeTeam/greptimedb` repository, and the agent asks you for the version and, if needed, the branch.1`, a new minor or major is cut from `main` (with an offer to create the release branch, with your consent), and a patch release uses the existing release branch that carries cherry-picked commits.
When should I use GreptimeDB Release Runbook?
GreptimeDB Release Runbook fits situations like: publishing a new GreptimeDB minor or major release; cutting a patch release from an existing release branch; checking that the Cargo version matches before tagging.
How do I install GreptimeDB Release Runbook in Claude Code?
Run `npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a claude-code`. Or copy the skill folder (.agents/skills/greptimedb-release in GreptimeTeam/greptimedb) into .claude/skills/greptimedb-release in your project. Claude Code loads it when a task matches its description.
How do I install GreptimeDB Release Runbook in Codex?
Run `npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a codex`. Or copy the skill folder (.agents/skills/greptimedb-release in GreptimeTeam/greptimedb) into .agents/skills/greptimedb-release in your project. Codex loads it when a task matches its description.
Can I use GreptimeDB Release Runbook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GreptimeTeam/greptimedb --skill greptimedb-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/greptimedb-release, .gemini/skills/greptimedb-release, .github/skills/greptimedb-release and .opencode/skills/greptimedb-release in your project.
What does GreptimeDB Release Runbook need to run?
Going by SKILL.md and its folder, GreptimeDB Release Runbook needs the command-line tools its instructions call (git and gh). Our summary lists: GitHub CLI `gh`, authenticated; `git`; `git cliff` and Python, for changelog generation through the release-note skill.
Does GreptimeDB Release Runbook access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is GreptimeDB Release Runbook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does GreptimeDB Release Runbook use?
GreptimeDB Release Runbook is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GreptimeDB Release Runbook use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GreptimeDB Release Runbook?
Skills that share tags, products or a category with GreptimeDB Release Runbook: Hunk Release Workflow (modem-dev/hunk, 9.6k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GreptimeDB Release Runbook?
GreptimeTeam (a GitHub organization) maintains it in GreptimeTeam/greptimedb, which has 6,729 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 10, 2026.
Source: GreptimeTeam/greptimedb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.