Agent skill

Release Deploy

DeskClaw 发版与部署流程助手。当用户提到"发版"、"release"、"部署"、"deploy"、 "promote"、"上线"、"发 beta"、"发 pre-release"时触发。根据用户意图生成完整的可执行命令，包含前置检查结果和操作确认清单。

Apache-2.0Auto-check: notesDevelopment

Install Release Deploy

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/release-deploy .claude/skills/release-deploy && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .claude/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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

$skill-installer install https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy

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

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/release-deploy .agents/skills/release-deploy && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .agents/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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.

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/release-deploy .cursor/skills/release-deploy && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .cursor/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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

$ gemini skills install https://github.com/NoDeskAI/nodeskclaw.git --path .cursor/skills/release-deploy

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/release-deploy .gemini/skills/release-deploy && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .gemini/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy

Installs 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).

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/release-deploy .github/skills/release-deploy && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .github/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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.

skills CLI

$ npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NoDeskAI/nodeskclaw release-deploy --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoDeskAI/nodeskclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/release-deploy .opencode/skills/release-deploy && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-deploy" agent skill from https://github.com/NoDeskAI/nodeskclaw/tree/main/.cursor/skills/release-deploy into .opencode/skills/release-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-deploy", 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-deploy
GitHub stars: 757
Token cost: ~928 tokens
SKILL.md length: 180 words
Files: 1
Skills in repo: 1
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Works in 3 steps: 解析用户意图 → 前置检查（只读命令，直接执行） → 输出操作确认清单
Development work in your project
SKILL.md covers 触发后的工作流程, 常见场景速查, CLI 参数速查 and 镜像仓库规则, plus 1 more section
Calls git

What it does

Release Deploy is an agent skill from NoDeskAI/nodeskclaw. DeskClaw 发版与部署流程助手。当用户提到"发版"、"release"、"部署"、"deploy"、 "promote"、"上线"、"发 beta"、"发 pre-release"时触发。根据用户意图生成完整的可执行命令，包含前置检查结果和操作确认清单。

Its SKILL.md is about 930 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. It works with GitHub and Git. The repository describes itself as: Humans and AI work together ❤️. The licence is Apache-2.0.

When your agent uses it

Development work in your project

Example prompts

“release”
“deploy”
“promote”
“/release-deploy”

Requirements

Docker

Workflow steps

3 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 8fbe26e. 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:
- git
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

Release Deploy loads about 928 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 180 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~37
When it runs · the whole SKILL.md, loaded when a task matches: ~928

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:132

- 配置位于 `deploy/.env.local`（不进 git）

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 NoDeskAI/nodeskclaw at commit 8fbe26e, republished under its Apache-2.0 licence (© NoDeskAI). 180 words, ~928 tokens.

Download SKILL.mdSave it as .claude/skills/release-deploy/SKILL.md (or your agent's skills folder).

name: release-deploy
description: DeskClaw 发版与部署流程助手。当用户提到"发版"、"release"、"部署"、"deploy"、 "promote"、"上线"、"发 beta"、"发 pre-release"时触发。根据用户意图生成完整的可执行命令，包含前置检查结果和操作确认清单。

DeskClaw 发版与部署

触发后的工作流程

1. 解析用户意图

从用户消息中提取以下参数：

参数	如何判断	默认值
操作类型	release / deploy / promote	必须明确
版本号	用户指定（如 v0.9.8-beta.1）	release/promote 必须指定
CE/EE	用户说"EE"或"含 admin" → `--ee`	CE（不加 --ee）
镜像源	用户说"国内源"/"mirrors"/"cn" → `--mirrors cn`	不加
目标环境	staging（默认）/ 生产（`--prod`）	staging
部署目标	all / backend / admin / portal / proxy	all
仅发版	用户说"只发版不部署" → 只运行 `release.sh create`	否
仅部署	用户说"不重新构建" → 只运行 `deploy.sh deploy --tag <version>`	否
本地分支部署	用户说"当前分支/本地分支部署" → 使用分支用途镜像 tag，禁止创建 git tag/GitHub Release	否

注意："部署当前分支"、"部署本地分支"只表示把当前工作树构建为镜像并部署，不等于发版授权。除非用户明确要求"发版"、"release"、"创建 tag"或"GitHub Release"，不得调用 deploy/release.sh create，不得创建或推送 git tag，不得创建 GitHub Release。

2. 前置检查（只读命令，直接执行）

bash

git status --short                        # 未提交变更
git tag -l '<version>*'                   # tag 是否已存在
git log --oneline -1                      # 最新 commit

EE 模式额外检查：

bash

ls -d ee/ 2>/dev/null                     # ee/ 目录存在
cd ee && git status --short               # EE 仓库状态

3. 输出操作确认清单

按以下格式输出。如果用户已经在同一请求中明确授权 AI 执行发版/部署，则可以直接执行；否则只给出可粘贴命令，等用户自己运行。

**发版目标**：<版本号> <CE/EE> <Pre-release/正式>

**当前状态**：
- CE 仓库：<干净/有未提交变更>
- EE 仓库：<干净/有未提交变更>（仅 EE 模式）
- 最新 commit：<hash> <message>
- tag <版本号>：<不存在/已存在>

**即将执行**：

| 步骤 | 命令 | 说明 |
|---|---|---|
| 1 | `./deploy/release.sh ...` | ... |
| 2 | `./deploy/deploy.sh ...` | ...（如有） |

**镜像分发**：
- backend/portal/proxy → <PUBLIC_REGISTRY 或 REGISTRY>
- admin → <REGISTRY>（仅 EE）

未授权 AI 执行时，请用户在终端运行以上命令。

重要：默认不得通过 Shell 工具运行 deploy/release.sh、deploy/deploy.sh、deploy/init.sh。只有用户在同一请求中明确授权 AI 执行发版/部署时，才允许运行；执行时必须显式带上 --context 和目标环境标志（--staging / --prod）。

常见场景速查

场景 A：EE Pre-release（如本次 v0.9.8-beta.1）

bash

# 1. 发版（构建镜像 + git tag + GitHub Pre-release）
./deploy/release.sh create <version> --ee --mirrors cn

# 2. 部署到生产（需用户明确授权）
./deploy/deploy.sh deploy all --tag <version> --ee --prod --context <CTX>

场景 B：CE Pre-release

bash

./deploy/release.sh create <version> --mirrors cn

场景 C：日常部署到生产

bash

./deploy/deploy.sh deploy all --tag <version> --prod --context <CTX>       # CE
./deploy/deploy.sh deploy all --tag <version> --ee --prod --context <CTX>  # EE
./deploy/deploy.sh deploy backend --tag <version> --prod --context <CTX>   # 只部署后端

场景 D：部署指定版本（不重新构建）

bash

./deploy/deploy.sh deploy all --tag <version> --prod --context <CTX>    # 生产
./deploy/deploy.sh deploy all --tag <version> --staging --context <CTX> # 可选临时 staging

场景 E：正式发布

bash

./deploy/deploy.sh deploy all --tag <version> --prod --context <CTX>
./deploy/release.sh finalize <version>

CLI 参数速查

参数	作用	适用命令
`--ee`	EE 模式（含 admin + ee/ 代码注入）	deploy, release
`--mirrors cn`	国内镜像源加速构建	deploy, release
`--prod`	部署到生产环境	deploy
`--tag <tag>`	指定镜像标签	deploy
`create`	构建推送镜像、创建 git tag 和 GitHub Pre-release	release.sh
`finalize`	将 GitHub Release 标记为正式版	release.sh
`--skip-proxy`	跳过 proxy 组件	deploy, release
`--no-cache`	Docker 不使用缓存	deploy, release
`--force`	跳过 Secret 差异确认	init

镜像仓库规则

get_component_registry("admin") → $REGISTRY（私有，EE 专用）
get_component_registry("其他") → $PUBLIC_REGISTRY（公开）或回退 $REGISTRY
配置位于 deploy/.env.local（不进 git）

Release Note / 公告称呼规则

对外 Release Note、群聊公告和发布摘要中，首次出现必须写成“DeskClaw 团队版 <version>”。
禁止写成“个人版”，也禁止省略“团队版”导致对外产品定位错误。
后文如需简称，必须先完整出现一次“DeskClaw 团队版”。

Files

Just SKILL.md in .cursor/skills/release-deploy of NoDeskAI/nodeskclaw.

Open the folder on GitHubat commit 8fbe26e

Compare with similar skills

Release Deploy 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.

Release Deploy compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Deploy this skillNoDeskAI/nodeskclaw	757	—	~928	Automated safety check: Notes	Apache-2.0	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	2 days ago
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	3 days ago
PR Review State Fetchprisma/orm	48k	—	~767	Automated safety check: Pass	Apache-2.0	today

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
69k GitHub starsUsed in 2 repos~1.1k tokens
DevelopmentAuto-check passed
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
57k GitHub stars~941 tokensUpdated 3 days ago
DevelopmentAuto-check passed
PR Review State Fetch
prisma/orm
Official
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
48k GitHub stars~767 tokensUpdated today
DevelopmentAuto-check passed
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
70k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed

Works with

Questions about Release Deploy

What does Release Deploy do?

DeskClaw 发版与部署流程助手。当用户提到"发版"、"release"、"部署"、"deploy"、 "promote"、"上线"、"发 beta"、"发 pre-release"时触发。根据用户意图生成完整的可执行命令，包含前置检查结果和操作确认清单。. Release Deploy is an agent skill from NoDeskAI/nodeskclaw.

When should I use Release Deploy?

Release Deploy fits situations like: development work in your project.

How do I install Release Deploy in Claude Code?

Run `npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a claude-code`. Or copy the skill folder (.cursor/skills/release-deploy in NoDeskAI/nodeskclaw) into .claude/skills/release-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Release Deploy in Codex?

Run `npx skills add NoDeskAI/nodeskclaw --skill release-deploy -a codex`. Or copy the skill folder (.cursor/skills/release-deploy in NoDeskAI/nodeskclaw) into .agents/skills/release-deploy in your project. Codex loads it when a task matches its description.

Can I use Release Deploy 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 NoDeskAI/nodeskclaw --skill release-deploy -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-deploy, .gemini/skills/release-deploy, .github/skills/release-deploy and .opencode/skills/release-deploy in your project.

What does Release Deploy need to run?

Going by SKILL.md and its folder, Release Deploy needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Release Deploy 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 Release Deploy safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Release Deploy use?

Release Deploy 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 Deploy use?

About 928 tokens (SKILL.md is roughly 3.7k 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 Deploy?

Skills that share tags, products or a category with Release Deploy: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Deploy?

NoDeskAI (a GitHub organization) maintains it in NoDeskAI/nodeskclaw, which has 757 GitHub stars. The repository was last updated on October 8, 2026.

Source: NoDeskAI/nodeskclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release Deploy

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DeskClaw 发版与部署

触发后的工作流程

1. 解析用户意图

2. 前置检查（只读命令，直接执行）

3. 输出操作确认清单

常见场景速查

场景 A：EE Pre-release（如本次 v0.9.8-beta.1）

场景 B：CE Pre-release

场景 C：日常部署到生产

场景 D：部署指定版本（不重新构建）

场景 E：正式发布

CLI 参数速查

镜像仓库规则

Release Note / 公告称呼规则

Files

Compare with similar skills

Similar skills

Contributor-First PR Merge

Create Pull Request

Pull Request Title and Body Writer

Draft Release Notes

PR Review State Fetch

Mole Release Notes Publisher

Related

Questions about Release Deploy