Mecatl Release Cutting
stacklok/mecatl
Cuts a tagged mecatl release by dispatching the release-PR workflow, merging the bot's pull request and verifying the tag, images, Helm chart, signed archives and Homebrew formula.
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks.
SKILL.md written in Chinese; this summary is our English description.
Install ccLoad Release Publisher
$ npx skills add caidaoli/ccLoad --skill ccload-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install caidaoli/ccLoad ccload-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/caidaoli/ccLoad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ccload-release .claude/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .claude/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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/caidaoli/ccLoad/tree/master/.agents/skills/ccload-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 caidaoli/ccLoad --skill ccload-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install caidaoli/ccLoad ccload-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ccload-release .agents/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .agents/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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 caidaoli/ccLoad --skill ccload-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install caidaoli/ccLoad ccload-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ccload-release .cursor/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .cursor/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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/caidaoli/ccLoad.git --path .agents/skills/ccload-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 caidaoli/ccLoad --skill ccload-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install caidaoli/ccLoad ccload-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ccload-release .gemini/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .gemini/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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 caidaoli/ccLoad ccload-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 caidaoli/ccLoad --skill ccload-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ccload-release .github/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .github/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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 caidaoli/ccLoad --skill ccload-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 caidaoli/ccLoad ccload-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ccload-release .opencode/skills/ccload-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 "ccload-release" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/ccload-release into .opencode/skills/ccload-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccload-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
ccload-release- GitHub stars
- 419
- Token cost
- ~887 tokens
- SKILL.md length
- 251 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks.
- Works in 5 steps: 检查 git status 和完整… → 从仓库根目录运行预览。默认渠道是 beta。工作区干净时运行 → 核对脚本输出的上一稳定版、上一有效 Beta、版本动作、目标… → …
- Publishing the next ccLoad Beta
- SKILL.md covers 参数契约, 版本规则, 发布流程 and 强制规则, plus 1 more section
- Runs Shell scripts from its folder; calls bash and git
What it does
This skill runs the release process for the ccLoad project. A single tag drives the repository's release workflow, so the agent must not create a Release by hand, trigger the workflow manually or publish the container image separately. Asking only for a version calculation or a preflight runs a dry run and reports the result without publishing, and editing the skill files never publishes.
The channel argument is beta or preview for the next Beta, or an explicit stable for a stable version, which is never guessed from tone; any other argument stops the run. Betas keep the major and minor version of the latest stable release and only bump the beta counter or patch, while a stable release computes standard SemVer from all commits since the last stable. If a Beta tag already changes the major or minor version, the run stops and reports it.
The flow checks git status and the diff, derives a single-line Conventional Commit subject, previews with scripts/release.sh in dry-run mode, then publishes with the publish flag. The script commits all changes, pushes master without force, waits for the Test workflow to pass, and then creates and pushes an annotated tag. The report lists the commit, master revision, tag, Release URL, Actions result and container image tags. The branch must be master and must not be behind or diverged from origin.
When your agent uses it
- Publishing the next ccLoad Beta
- Cutting an explicit stable ccLoad release
- Previewing the next version number and tag without releasing
Example prompts
- “Release the next ccLoad beta.”
- “Do a dry run of a stable release and show me the target tag.”
- “ccload-release stable”
Requirements
- A ccLoad checkout on the master branch
- Push access and GitHub Actions for the repository
- bash to run scripts/release.sh
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 检查 git status 和完整 diff。工作区有改动时，根据实际改动推导一个单行 Conventional Commit subject；必须准确反映最高语义版本影响，禁止使用掩盖功能变更的通用 chore。不要为提交或推送重复询问用户。
- 从仓库根目录运行预览。默认渠道是 beta。工作区干净时运行
- 核对脚本输出的上一稳定版、上一有效 Beta、版本动作、目标 Tag、工作区动作和分支动作。用户调用本 Skill 已经授权自动提交、非强制推送 master 和发布；目标符合参数契约时直接继续。
- 执行发布。工作区干净时运行
- 报告自动创建的提交（如有）、推送的 master 修订、目标 Tag、GitHub Release URL 和 Actions 结果。稳定版报告 ghcr.io/caidaoli/ccload: 和 ghcr.io/caidaoli/ccload:latest（该稳定版为…
What it can do on your machine
Read from SKILL.md and the folder at commit 28898f0. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
bashgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
ccLoad Release Publisher loads about 887 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 251 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); the scripts in this folder are not scanned.
SKILL.md
The full file from caidaoli/ccLoad at commit 28898f0, republished under its MIT licence (© caidaoli). 251 words, ~887 tokens.
Download SKILL.mdSave it as
.claude/skills/ccload-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- ccload-release
- description
- 发布 ccLoad Beta 或显式 stable 版本，完成提交、推送、CI、Release 和镜像验证；仅检查或修改发布流程时不执行发布。
发布 ccLoad
通过唯一的 Tag 驱动 .github/workflows/release.yml。不要手动创建 Release、手动触发发布工作流或单独发布容器镜像。
只要求计算版本或预检时，执行下方对应的 dry-run 并报告结果，不进入 publish。用户要求发布或单独调用本技能（可带通道参数）才适用自动提交、推送和发布授权；编辑技能文件不执行发布。
参数契约
$ccload-release、/ccload-release、ccload-release beta、ccload-release preview：发布下一个 Beta。ccload-release stable：发布稳定版。必须有显式stable参数；禁止根据语气猜测。- 其他参数：停止并报告只支持
beta、preview、stable。
Tag 形状固定：
- Beta：
vX.Y.Z-beta.N - 稳定版：
vX.Y.Z
版本规则
- Beta 必须锁定最近稳定版
vX.Y.S的主版本X和次版本Y，禁止因feat或 breaking change 生成vX.(Y+1).0-beta.N或v(X+1).0.0-beta.N。 - 最近稳定版之后没有有效 Beta 时，发布
vX.Y.(S+1)-beta.1。 - 已有
vX.Y.P-beta.N时，只检查该 Beta Tag 之后的新提交：- 小修改（没有
feat、!或BREAKING CHANGE）保持X.Y.P，发布vX.Y.P-beta.(N+1)。 - 大修改（存在
feat、!或BREAKING CHANGE）只把 patch 加一并重置序号，发布vX.Y.(P+1)-beta.1。
- 小修改（没有
- 只有显式
stable发布才从最近稳定版后的全部提交计算标准 SemVer：breaking change 增加主版本，feat增加次版本，其余增加 patch。Beta 永远不修改主版本或次版本。 - 最近稳定版之后如果已存在修改主版本或次版本的可达 Beta Tag，立即停止发布并报告非法 Tag；禁止继续制造互相冲突的预览版本。
发布流程
检查
git status和完整 diff。工作区有改动时，根据实际改动推导一个单行 Conventional Commit subject；必须准确反映最高语义版本影响，禁止使用掩盖功能变更的通用chore。不要为提交或推送重复询问用户。从仓库根目录运行预览。默认渠道是
beta。工作区干净时运行：bash bash .agents/skills/ccload-release/scripts/release.sh beta --dry-run工作区有改动时传入推导出的提交 subject：
bash bash .agents/skills/ccload-release/scripts/release.sh beta --dry-run --commit-message 'feat(scope): summary'稳定版把
beta改为stable。核对脚本输出的上一稳定版、上一有效 Beta、版本动作、目标 Tag、工作区动作和分支动作。用户调用本 Skill 已经授权自动提交、非强制推送
master和发布；目标符合参数契约时直接继续。执行发布。工作区干净时运行：
bash bash .agents/skills/ccload-release/scripts/release.sh beta --publish工作区有改动时必须复用 dry-run 的同一个 subject：
bash bash .agents/skills/ccload-release/scripts/release.sh beta --publish --commit-message 'feat(scope): summary'稳定版把
beta改为stable。脚本会自动git add -A、创建提交、非强制推送master，等待该提交对应的Testworkflow 全部成功，确认远端仍精确一致后再创建并推送 annotated Tag。本地已有未推送提交时不创建额外提交，直接推送并等待 CI。报告自动创建的提交（如有）、推送的
master修订、目标 Tag、GitHub Release URL 和 Actions 结果。稳定版报告ghcr.io/caidaoli/ccload:<tag>和ghcr.io/caidaoli/ccload:latest（该稳定版为 SemVer 最高版本时beta别名同步指向它，一并报告）；Beta 报告ghcr.io/caidaoli/ccload:<tag>和ghcr.io/caidaoli/ccload:beta。
强制规则
- 当前分支必须是
master。本地master可与origin/master相等或领先；远端领先或双方分叉时停止，禁止自动 pull、merge、rebase 或 force-push。 - Beta 的目标 Tag 必须遵守“固定最近稳定版主版本和次版本”的版本规则；脚本输出出现 minor/major Beta 增量时必须停止。
- dry-run 不提交、不推送、不打 Tag。publish 自动提交全部当前工作区改动；禁止 amend、拆改已有提交或修改版本文件。
Testworkflow 是提交级唯一发布门禁，必须覆盖后端测试、Web 验证、构建、lint 和 PostgreSQL 集成测试。发布脚本必须按完整 commit SHA 找到并等待该 workflow；找不到、被取消或失败时不得创建 Tag。- 分支推送只能是普通 fast-forward push。推送后以及
Testworkflow 成功后都必须重新 fetch 并确认本地HEAD等于origin/master，才能创建 Tag。CI 失败时保留已经推送的提交，不自动回滚。 - Beta Release 必须是 prerelease 且不得成为 latest；稳定版 Release 必须成为 latest。
- 每个 Release 都发布 GHCR 多架构镜像。稳定版必须同时打精确版本 Tag 和
latest；Beta 必须同时打精确版本 Tag 和beta；精确标签与对应浮动别名必须指向同一镜像摘要。beta别名指向全渠道 SemVer 最高版本：稳定版发布时若不存在更高的 Beta Tag，beta同步推进到该稳定版；存在更高 Beta 时保持不动，禁止降级。 - Release Notes 按发布通道比较：稳定版只比较上一个可达稳定版；新稳定版之后的首个 Beta 与该稳定版比较，后续 Beta 才与同一稳定版之后的上一个 Beta 比较。
- 分支或发布失败后保留现场并报告本地提交、失败的 Tag/Actions URL。不要自动删提交、Tag、Release 或镜像；回滚必须由用户另行明确授权。
- 不绕过
.github/workflows/release.yml的 Tag 校验，也不创建beta、latest这类浮动 Git Tag；它们只允许作为 GHCR 镜像别名由发布工作流管理。
脚本自检
修改发布脚本后运行：
bash .agents/skills/ccload-release/scripts/release.sh --self-test© caidaoli, MIT. 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 2 other files (scripts) in .agents/skills/ccload-release of caidaoli/ccLoad.
- SKILL.md
- agents/openai.yaml
- scripts/release.sh
Open the folder on GitHubat commit 28898f0
Compare with similar skills
ccLoad Release Publisher 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 |
|---|---|---|---|---|---|---|
| ccLoad Release Publisher this skillcaidaoli/ccLoad | 419 | — | ~887 | Automated safety check: Pass | MIT | |
| Mecatl Release Cuttingstacklok/mecatl | 254 | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| ClickUp CLI Release Processkrodak/clickup-cli | 123 | — | ~906 | Automated safety check: Warn | MIT | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 9.2k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
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.
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.
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.
npm Package Publisher
klaudworks/universal-skills
Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.
More from caidaoli/ccLoad
CLIProxy Core Sync
caidaoli/ccLoad
Syncs or audits ccLoad's CLIProxyAPI protocol-conversion core and registered provider adapters against one pinned upstream commit, then verifies the result.
Related
Categories
Questions about ccLoad Release Publisher
What does ccLoad Release Publisher do?
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks. This skill runs the release process for the ccLoad project. A single tag drives the repository's release workflow, so the agent must not create a Release by hand, trigger the workflow manually or publish the container image separately.
When should I use ccLoad Release Publisher?
ccLoad Release Publisher fits situations like: publishing the next ccLoad Beta; cutting an explicit stable ccLoad release; previewing the next version number and tag without releasing.
How do I install ccLoad Release Publisher in Claude Code?
Run `npx skills add caidaoli/ccLoad --skill ccload-release -a claude-code`. Or copy the skill folder (.agents/skills/ccload-release in caidaoli/ccLoad) into .claude/skills/ccload-release in your project. Claude Code loads it when a task matches its description.
How do I install ccLoad Release Publisher in Codex?
Run `npx skills add caidaoli/ccLoad --skill ccload-release -a codex`. Or copy the skill folder (.agents/skills/ccload-release in caidaoli/ccLoad) into .agents/skills/ccload-release in your project. Codex loads it when a task matches its description.
Can I use ccLoad Release Publisher 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 caidaoli/ccLoad --skill ccload-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/ccload-release, .gemini/skills/ccload-release, .github/skills/ccload-release and .opencode/skills/ccload-release in your project.
What does ccLoad Release Publisher need to run?
Going by SKILL.md and its folder, ccLoad Release Publisher needs a shell for the scripts in its folder and the command-line tools its instructions call (bash and git). Our summary lists: A ccLoad checkout on the master branch; Push access and GitHub Actions for the repository; bash to run scripts/release.sh.
Does ccLoad Release Publisher access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is ccLoad Release Publisher 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does ccLoad Release Publisher use?
ccLoad Release Publisher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does ccLoad Release Publisher use?
About 887 tokens (SKILL.md is roughly 3.5k 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 ccLoad Release Publisher?
Skills that share tags, products or a category with ccLoad Release Publisher: Mecatl Release Cutting (stacklok/mecatl, 254 stars), ClickUp CLI Release Process (krodak/clickup-cli, 123 stars), OpenWork Release Process (different-ai/openwork, 24k stars) and Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains ccLoad Release Publisher?
caidaoli (a GitHub user) maintains it in caidaoli/ccLoad, which has 419 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.
Source: caidaoli/ccLoad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.