Agent skill

Release

发布 NcatBot 新版本到 PyPI 和 GitHub Release，或仅编排 Commit 推送到 main。从工作区变更编排 commit 到最终发布的全链路流程。Use when: 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送。

MITAuto-check passedDevelopment

Install Release

skills CLI

$ npx skills add ncatbot/NcatBot --skill release -a claude-code

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

GitHub CLI

$ gh skill install ncatbot/NcatBot release --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/ncatbot/NcatBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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

$skill-installer install https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release

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 ncatbot/NcatBot --skill release -a codex

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

GitHub CLI

$ gh skill install ncatbot/NcatBot release --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/ncatbot/NcatBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release .agents/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

skills CLI

$ npx skills add ncatbot/NcatBot --skill release -a cursor

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

GitHub CLI

$ gh skill install ncatbot/NcatBot release --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/ncatbot/NcatBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release .cursor/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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

$ gemini skills install https://github.com/ncatbot/NcatBot.git --path .agents/skills/release

--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 ncatbot/NcatBot --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install ncatbot/NcatBot release --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/ncatbot/NcatBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release .gemini/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

GitHub CLI

$ gh skill install ncatbot/NcatBot release

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 ncatbot/NcatBot --skill release -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/ncatbot/NcatBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release .github/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

skills CLI

$ npx skills add ncatbot/NcatBot --skill release -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 ncatbot/NcatBot release --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/ncatbot/NcatBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release .opencode/skills/release && 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" agent skill from https://github.com/ncatbot/NcatBot/tree/main/.agents/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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: release
GitHub stars: 115
Token cost: ~513 tokens
SKILL.md length: 181 words
Files: 8 (incl. scripts, references)
Skills in repo: 12
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 5 steps: 同步远端（不可跳过） — git pull --rebase origin… → Commit 编排 — 处理未提交变更（含 docs submodule）→… → 审查历史 commits + 生成 Release Notes — 确认哪些进… → …
: 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送
SKILL.md covers 模式判断, 发布模式, 推送模式 and 前置条件, plus 2 more sections
Runs Python scripts from its folder; calls git and gh; needs PYPI_TOKEN

What it does

Release is an agent skill from ncatbot/NcatBot. 发布 NcatBot 新版本到 PyPI 和 GitHub Release，或仅编排 Commit 推送到 main。从工作区变更编排 commit 到最终发布的全链路流程。Use when: 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送。

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/asset-update.md`, `references/ci-publish.md` and `references/commit-workflow.md`).

It sits in Development, covering Changelog and release notes. It works with GitHub and Git. The repository describes itself as: NapCat Python SDK；快速开发你的 QQ 机器人. The licence is MIT.

When your agent uses it

: 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送
Tasks that involve Changelog and release notes

Example prompts

“/release”

Requirements

Python 3
A credential in PYPI_TOKEN

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

同步远端（不可跳过） — git pull --rebase origin main。即使刚做完 commit 编排，也必须在生成 release notes 前拉取远端，否则 git log 看不到其他人合入的 PR/commit，release notes 会缺失内容。
Commit 编排 — 处理未提交变更（含 docs submodule）→ 参见 commit-workflow.md
审查历史 commits + 生成 Release Notes — 确认哪些进 release notes，确定版本号 → 参见 versioning.md
本地预检 + 分步推送 tag — ruff + pytest → 确保 pyproject.toml 的版本号正确 → push branch + push tag → 参见 ci-publish.md
（备用）本地人工发布 — CI 不可用时 → 参见 local-publish.md

What it can do on your machine

Read from SKILL.md and the folder at commit c26300a. 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 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- git
- gh
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 these keys or tokens, usually read from environment variables:
- PYPI_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release loads about 513 tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 181 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~513
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.7k

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 ncatbot/NcatBot at commit c26300a, republished under its MIT licence (© ncatbot). 181 words, ~513 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: release
description: 发布 NcatBot 新版本到 PyPI 和 GitHub Release，或仅编排 Commit 推送到 main。从工作区变更编排 commit 到最终发布的全链路流程。Use when: 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送。
license: MIT

Release Skill

你是 NcatBot 发布助手，负责从工作区变更到版本发布的全链路流程。

模式判断

自动检查工作区变更 + 待推送 commits，判断是否涉及核心路径：

核心路径	`ncatbot/` · `pyproject.toml` · `main.py`
发布模式	检测到重大变动时或用户明确要求发布时
推送模式	用户明确要求推送时

docs 是 Git submodule，其指针变更在 git diff 中显示为 docs（无斜杠），不触发发布模式。

发布模式

主要方式：推送 v* tag → CI 自动完成 lint → test → build → PyPI → GitHub Release。

流程：

同步远端（不可跳过） — git pull --rebase origin main。即使刚做完 commit 编排，也必须在生成 release notes 前拉取远端，否则 git log 看不到其他人合入的 PR/commit，release notes 会缺失内容。
Commit 编排 — 处理未提交变更（含 docs submodule）→ 参见 commit-workflow.md
审查历史 commits + 生成 Release Notes — 确认哪些进 release notes，确定版本号 → 参见 versioning.md
本地预检 + 分步推送 tag — ruff + pytest → 确保 pyproject.toml 的版本号正确 → push branch + push tag → 参见 ci-publish.md
（备用）本地人工发布 — CI 不可用时 → 参见 local-publish.md

推送模式

流程：

同步远端 — git pull --rebase origin main
Commit 编排 — 同发布模式步骤 2 → 参见 commit-workflow.md
推送 — git push origin main
（按需）更新 Release Asset — 若 commit 涉及 docs/skills → 参见 asset-update.md

前置条件

Python 虚拟环境已激活：.venv\Scripts\activate.ps1
GitHub CLI 已登录：gh auth login --web
GitHub Secrets 已配置 PYPI_TOKEN（CI 使用）
docs submodule 已初始化：git submodule update --init

关键约束

测试优先：CI 中 pytest 全部通过才执行发布；本地预检同样不可跳过
先 commit 再定版本：版本号取决于本次 commits 的变更类型
分步推送：先推 branch，再推 tag，避免重复触发 CI
major 由人类决定：AI 不主动提及、不建议 major 升版
docs 变更先进子仓库：主仓库只提交 submodule 指针更新

ASK 决策点

触发条件	询问内容
模式无法自动判断	发布 or 推送
未明确且无法自动推断版号	版本号策略

Files

SKILL.md and 7 other files (scripts, references) in .agents/skills/release of ncatbot/NcatBot.

SKILL.md
references/asset-update.md
references/ci-publish.md
references/commit-workflow.md
references/local-publish.md
references/versioning.md
scripts/pack_user_ref.py
scripts/precheck.py

Open the folder on GitHubat commit c26300a

Compare with similar skills

Release 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 compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release this skillncatbot/NcatBot	115	—	~513	Automated safety check: Pass	MIT	3 days ago
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	yesterday
Mole Release Notes Publishertw93/Mole	69k	—	~1.9k	Automated safety check: Pass	GPL-3.0	yesterday
Release Bumpjamiepine/voicebox	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Go-Redis Release Preparationredis/go-redis	22k	—	~1.1k	Automated safety check: Pass	BSD-2-Clause	yesterday

Similar skills

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 yesterday
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.
69k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Go-Redis Release Preparation
redis/go-redis
Official
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
22k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
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.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Release

What does Release do?

When should I use Release?

Release fits situations like: : 发版、release、发布、changelog、版本号、pick commits、挑选提交、release notes、编排 commit、push、推送; tasks that involve Changelog and release notes.

How do I install Release in Claude Code?

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

How do I install Release in Codex?

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

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

What does Release need to run?

Going by SKILL.md and its folder, Release needs Python for the scripts in its folder, the command-line tools its instructions call (git and gh) and credentials named PYPI_TOKEN. Our summary lists: Python 3; A credential in PYPI_TOKEN.

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

Release is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release use?

About 513 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 69k stars), Release Bump (jamiepine/voicebox, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

ncatbot (a GitHub organization) maintains it in ncatbot/NcatBot, which has 115 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 4, 2026.

Source: ncatbot/NcatBot 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

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

Release Skill

模式判断

发布模式

推送模式

前置条件

关键约束

ASK 决策点

Files

Compare with similar skills

Similar skills

More from ncatbot/NcatBot

Related

Questions about Release