Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Guide for cutting a new release of the GenAI Factory repository.
Install Release Process
$ npx skills add GoogleCloudPlatform/genai-factory --skill release-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/genai-factory release-process --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/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-process .claude/skills/release-process && 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 "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .claude/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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/GoogleCloudPlatform/genai-factory/tree/master/skills/release-processType 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 GoogleCloudPlatform/genai-factory --skill release-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/genai-factory release-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-process .agents/skills/release-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .agents/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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 GoogleCloudPlatform/genai-factory --skill release-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/genai-factory release-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-process .cursor/skills/release-process && 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 "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .cursor/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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/GoogleCloudPlatform/genai-factory.git --path skills/release-process--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 GoogleCloudPlatform/genai-factory --skill release-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/genai-factory release-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-process .gemini/skills/release-process && 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 "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .gemini/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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 GoogleCloudPlatform/genai-factory release-processInstalls 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 GoogleCloudPlatform/genai-factory --skill release-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-process .github/skills/release-process && 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 "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .github/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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 GoogleCloudPlatform/genai-factory --skill release-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GoogleCloudPlatform/genai-factory release-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/genai-factory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-process .opencode/skills/release-process && 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 "release-process" agent skill from https://github.com/GoogleCloudPlatform/genai-factory/tree/master/skills/release-process into .opencode/skills/release-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-process", 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
release-process- GitHub stars
- 174
- Token cost
- ~1.3k tokens
- SKILL.md length
- 569 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guide for cutting a new release of the GenAI Factory repository.
- Works in 7 steps: Preparation → Review the Changes Since the Last Release → Check the Cloud Foundation Fabric… → …
- Asked to create
- SKILL.md covers Prerequisites, 1. Preparation, 2. Review the Changes Since… and 3. Check the Cloud Foundation…, plus 4 more sections
- Calls git, gh and uv
What it does
Release Process is an agent skill from GoogleCloudPlatform/genai-factory. Guide for cutting a new release of the GenAI Factory repository. Use this skill when asked to create, prepare, or draft a new release.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Deployment and Changelog and release notes. It works with GitHub, Google Cloud and GitHub Actions. The repository describes itself as: A collection of end-to-end infrastructure blueprints to deploy generative AI infrastructures in GCP, using IaC and following security best-practices. The licence is Apache-2.0.
When your agent uses it
- Asked to create
- Draft a new release
Example prompts
- “/release-process”
Requirements
- Python 3
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 624ada4. 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:
gitghuv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and uv, 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
Release Process loads about 1.3k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 569 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 GoogleCloudPlatform/genai-factory at commit 624ada4, republished under its Apache-2.0 licence (© GoogleCloudPlatform). 569 words, ~1,320 tokens.
Download SKILL.mdSave it as
.claude/skills/release-process/SKILL.md (or your agent's skills folder).- name
- release-process
- description
- Guide for cutting a new release of the GenAI Factory repository. Use this skill when asked to create, prepare, or draft a new release.
GenAI Factory Release Process
This skill guides maintainers through the process of cutting a new release for the GenAI Factory repository.
CRITICAL: Release names and tags MUST ALWAYS be prefixed with
v(e.g.,v2.0.0,v2.1.0).
GenAI Factory has no CHANGELOG.md and no changelog tooling: releases are GitHub releases whose notes combine a short hand-written summary with GitHub's auto-generated commit list.
Prerequisites
- Permissions: You must have write/release permissions on the repository.
- GitHub CLI: An authenticated
gh(check withgh auth status). - Environment: Python dependencies installed with
uv sync --all-groups, plusterraformandgcloudif you intend to run the tests locally.
1. Preparation
Start from the master branch and ensure you are up to date:
git checkout master
git pullIdentify the latest released version:
LATEST_RELEASE=$(git tag --sort=-v:refname | head -n 1)
echo "Latest release is: $LATEST_RELEASE"Confirm master is green before releasing — the nightly Linting, Tests, and Integration Tests workflows all gate the release:
gh run list --branch master --limit 10If anything is red, fix it (or wait for the fix to merge) before proceeding.
2. Review the Changes Since the Last Release
Collect what went in, which also determines the bump type:
git log --oneline $LATEST_RELEASE..HEAD
gh pr list --state merged --base master --limit 50 \
--json number,title,mergedAt,url \
--jq '.[] | "\(.number)\t\(.title)"'Choose the bump:
- major — very important refactoring, which usually involve deep refactoring of the user deployments or that cause lots of recreate states.
- minor — new version of Cloud Foundation Fabric referenced by all modules of the factories, new factories, new sample applications, new features on existing stages.
- patch — fixes, dependency and security upgrades, documentation only.
Read the merged PR titles and summarize what's in the bodies: those are what the release notes must surface.
NEW_RELEASE="v2.1.0" # set to the version you decided on
echo "New release is: $NEW_RELEASE"3. Check the Cloud Foundation Fabric Compatibility Statement
Every factory pins the same Fabric tag.
Verify the pin and make sure the compatibility statement in the main README.md matches it:
grep -rho "ref=v[0-9.]*" --include="*.tf" . | sort -u
grep -n "Cloud Foundation Fabric" README.md | headIf the statement is stale, update it in a normal PR (or a small commit on master) before cutting the release, so the tag points at accurate documentation. The pinned ref itself is bumped by the nightly integration workflow, which opens an [GH Actions] Update Fabric to <tag> PR; do not bump it by hand as part of the release.
Show full SKILL.md (235 more words)Show less
4. Run the Checks Locally
uv run pre-commit run --all-files
uv run pytest -n4 testsBoth must pass on the exact commit you are about to tag.
5. Draft the Release Notes
Write the notes in the style of the previous releases (gh release view $LATEST_RELEASE to see one). The structure is:
## What's Changed
<one or two sentences describing the theme of the release>
**New Factories**
* ...
**New Features**
* ...
**Compatibility with Cloud Foundation Fabric**
* Compatible with Cloud Foundation Fabric <tag>.
**Fixes, security upgrades**
* ...CRITICAL: Show the drafted notes to the user and wait for their approval before creating the release.
6. Create the GitHub Release
You can create the release either automatically via the GitHub CLI or manually via the GitHub UI.
Option A: Automated via GitHub CLI (Recommended)
Write the approved notes to a file using your file-writing tool (not a heredoc or shell redirection: backticks in the notes would be evaluated by the shell), then create the release. --generate-notes appends GitHub's auto-generated commit and contributor list, including the "Full Changelog" link, after your hand-written notes.
gh release create "$NEW_RELEASE" \
--target master \
--title "$NEW_RELEASE" \
--notes-file /tmp/release-notes.md \
--generate-notesgh creates the tag on --target for you, so there is no separate git tag step.
Option B: Manual via GitHub UI
Go to the GitHub Releases UI and configure the release:
- Tag: Create a new tag matching the new version (e.g.,
v2.1.0), targetingmaster. - Title: Use the exact same version string as the tag.
- Release Notes: Click the "Generate release notes" button, then paste your hand-written notes at the top of the generated content.
Click Publish release.
7. Verify
gh release view "$NEW_RELEASE"
git fetch --tagsCheck that the tag points at the intended commit and that the notes render as expected.
© GoogleCloudPlatform, 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
Just SKILL.md in skills/release-process of GoogleCloudPlatform/genai-factory.
Open the folder on GitHubat commit 624ada4
Compare with similar skills
Release Process 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 |
|---|---|---|---|---|---|---|
| Release Process this skillGoogleCloudPlatform/genai-factory | 174 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| EverOS Release WorkflowEverMind-AI/EverOS | 13k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Remotion Bits Releaseav/remotion-bits | 486 | — | ~1.2k | Automated safety check: Pass | None |
Similar skills
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
Remotion Bits Release
av/remotion-bits
Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm 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.
Related
Works with
Categories
Questions about Release Process
What does Release Process do?
Guide for cutting a new release of the GenAI Factory repository. Release Process is an agent skill from GoogleCloudPlatform/genai-factory. Guide for cutting a new release of the GenAI Factory repository.
When should I use Release Process?
Release Process fits situations like: asked to create; draft a new release.
How do I install Release Process in Claude Code?
Run `npx skills add GoogleCloudPlatform/genai-factory --skill release-process -a claude-code`. Or copy the skill folder (skills/release-process in GoogleCloudPlatform/genai-factory) into .claude/skills/release-process in your project. Claude Code loads it when a task matches its description.
How do I install Release Process in Codex?
Run `npx skills add GoogleCloudPlatform/genai-factory --skill release-process -a codex`. Or copy the skill folder (skills/release-process in GoogleCloudPlatform/genai-factory) into .agents/skills/release-process in your project. Codex loads it when a task matches its description.
Can I use Release Process 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 GoogleCloudPlatform/genai-factory --skill release-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-process, .gemini/skills/release-process, .github/skills/release-process and .opencode/skills/release-process in your project.
What does Release Process need to run?
Going by SKILL.md and its folder, Release Process needs the command-line tools its instructions call (git, gh and uv). Our summary lists: Python 3.
Does Release Process access the network?
SKILL.md contains no URLs. Its commands use git, gh and uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Process 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 Release Process use?
Release Process 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 Release Process use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Release Process?
Skills that share tags, products or a category with Release Process: Cline CLI Release Publisher (cline/cline, 70k stars), OpenWork Release Process (different-ai/openwork, 24k stars), Cline Desktop App Release (cline/cline, 70k stars) and EverOS Release Workflow (EverMind-AI/EverOS, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Process?
GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/genai-factory, which has 174 GitHub stars. The repository was last updated on October 5, 2026.
Source: GoogleCloudPlatform/genai-factory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.