Agent skill

Ant Design Mobile Release

by ant-design in ant-design/ant-design-mobile

Prepares an npm release of ant-design-mobile up to the version commit, then tags and publishes the GitHub Release after you run the publish command yourself.

MITAuto-check passedDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install Ant Design Mobile Release

skills CLI
$ npx skills add ant-design/ant-design-mobile --skill antd-mobile-release -a claude-code

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

GitHub CLI
$ gh skill install ant-design/ant-design-mobile antd-mobile-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/ant-design/ant-design-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/antd-mobile-release .claude/skills/antd-mobile-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/

Facts

Skill name
antd-mobile-release
GitHub stars
12k
Token cost
~497 tokens
SKILL.md length
161 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Prepares an npm release of ant-design-mobile up to the version commit, then tags and publishes the GitHub Release after you run the publish command yourself.

  • Works in 3 steps: 只读检查当前分支、工作区、最新 master、已有 Git tag、GitHub… → 根据变更性质推荐一个明确的目标版本,简述推荐理由,并直接询问用户是否采用该版本;用… → 得到用户对目标版本的明确确认后,才修改文件、安装依赖、编译、提交或推送。确认目标版…
  • Preparing a new npm release of ant-design-mobile
  • SKILL.md covers 先确认版本, 确认后执行准备 and 用户手工发布完成后
  • Calls pnpm and npm

What it does

Written in Chinese, the skill splits a release into two phases around a manual step. First the agent inspects the branch, working tree, latest master, existing tags, releases and npm versions, recommends a target version with a reason, and waits for your explicit confirmation; a stable release cannot reuse the current alpha version number, and a pre-release needs a version plus an alpha or dev tag. Only after confirmation does it change files, install dependencies, build, commit or push.

Preparation sets package.json to the confirmed version, runs pnpm build, applicable tests and lint, pnpm package-diff and an npm pack dry run on ./lib, and makes a commit whose title carries the full version in the form chore: release v followed by the number. It pushes to origin/master, reports CI, drafts bilingual Chinese and English release notes, and then only tells you which command to type: pnpm pub for stable, or pnpm pub:alpha or pnpm pub:dev for pre-releases. Once you say publishing is done, it checks the npm version and dist-tag, waits out registry delay, creates the version tag, makes the GitHub Release and follows the Doc Site workflow.

When your agent uses it

  • Preparing a new npm release of ant-design-mobile
  • Tagging and creating the GitHub Release after a manual npm publish
  • Checking npm versions, tags and releases before choosing a version number
  • Drafting bilingual release notes covering changes since the last stable version

Example prompts

  • “Prepare a release for ant-design-mobile and recommend a version.”
  • “I have run pnpm pub. Verify the npm package, then tag and create the GitHub Release.”
  • “Prepare an alpha pre-release of ant-design-mobile and tell me which publish command to run.”

Requirements

  • The ant-design-mobile repository with pnpm and npm
  • Permission to push to origin/master and create GitHub Releases

Workflow steps

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

  1. 只读检查当前分支、工作区、最新 master、已有 Git tag、GitHub Release、npm 版本与 dist-tag,以及上次发布以来的变更。已有未提交改动时先查明归属,不覆盖用户工作。
  2. 根据变更性质推荐一个明确的目标版本,简述推荐理由,并直接询问用户是否采用该版本;用户也可以指定其他版本。稳定版不能沿用当前的 -alpha 版本号;预发布版需明确版本号及 alpha 或 dev 标签。
  3. 得到用户对目标版本的明确确认后,才修改文件、安装依赖、编译、提交或推送。确认目标版本尚未用于 npm 包、Git tag 或 GitHub Release。

What it can do on your machine

Read from SKILL.md and the folder at commit eee5477. 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:

    • pnpm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and npm, 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

Ant Design Mobile Release loads about 497 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 161 words of instructions outside code blocks.

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

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 ant-design/ant-design-mobile at commit eee5477, republished under its MIT licence (© ant-design). 161 words, ~497 tokens.

Download SKILL.mdSave it as .claude/skills/antd-mobile-release/SKILL.md (or your agent's skills folder).
name
antd-mobile-release
description
在 ant-design-mobile 仓库准备 npm 发版,并在用户手工发布后创建 Git tag 和 GitHub Release 时使用。

Ant Design Mobile 发版

适用于 ant-design/ant-design-mobile 的 npm 包和 GitHub Release。用户要求“发布准备”时,先确认版本,再完成依赖、构建、检查和版本提交;用户只手工执行 npm 发布命令。用户告知发布完成后,由 Agent 验证 npm 包,再打 tag 和创建 GitHub Release。

先确认版本

  1. 只读检查当前分支、工作区、最新 master、已有 Git tag、GitHub Release、npm 版本与 dist-tag,以及上次发布以来的变更。已有未提交改动时先查明归属,不覆盖用户工作。
  2. 根据变更性质推荐一个明确的目标版本,简述推荐理由,并直接询问用户是否采用该版本;用户也可以指定其他版本。稳定版不能沿用当前的 -alpha 版本号;预发布版需明确版本号及 alpha 或 dev 标签。
  3. 得到用户对目标版本的明确确认后,才修改文件、安装依赖、编译、提交或推送。确认目标版本尚未用于 npm 包、Git tag 或 GitHub Release。

确认后执行准备

  1. 基于最新 master,检查工作区和远端 CI。按锁文件安装依赖,使用与项目兼容的 Node.js、pnpm 版本,不顺手升级依赖或修改包管理配置。
  2. 将 package.json 改为确认的目标版本。执行 pnpm build、适用的测试与 Lint、pnpm package-diff 和 npm pack --dry-run ./lib,核对 lib/package.json 与目标版本、待发布文件一致;失败时先修复并重新验证,不带着失败结果提交。
  3. 只提交本次发版相关文件。版本提交标题必须写明完整目标版本,使用 chore: release v<version>,例如 chore: release v5.43.0;不得使用 chore: change version 等不含版本号的泛化标题。提交后核对标题与 package.json 版本一致,再推送至 origin/master,核对远端提交与本地一致,并报告远端 CI 状态。不能安全更新或推送时,说明阻塞,不覆盖他人改动。
  4. 整理上个稳定版以来的变更,准备简洁的中英文 GitHub Release 日志及相关 PR 链接。确保用户所在工作目录已有正确版本的 ./lib,且 Node.js、pnpm 和 npm registry 可直接用于发包;准备阶段不创建或推送 tag,不运行发布命令,也不创建 GitHub Release。报告版本、提交和检查结果,然后只提示稳定版用户输入 pnpm pub。用户明确选择预发布版时,改为对应的 pnpm pub:alpha 或 pnpm pub:dev。

用户手工发布完成后

  1. 用户告知发布完成后,从目标 npm registry 核对实际包版本与 dist-tag;稳定版应成为 latest。npm 发布成功后可能延迟可见,暂时查不到目标版本或标签仍是旧版本时,先核对发布命令输出和 registry,再每隔 30–60 秒重新查询并向用户报告等待状态,不把短暂的 404 当作发布失败。确认目标版本及标签可见前,不得打 tag 或创建 Release,也不要代替用户重试 npm 发布;若长时间仍不可见,再排查发布结果。
  2. 确认远端 master 包含版本提交。在该版本提交上创建并推送 v<version> tag;若 tag 已存在,核对其指向,正确则复用,错误则先处理冲突,不移动已发布的 tag。
  3. 用准备好的中英文日志在该 tag 上创建 GitHub Release;若 Release 已存在,则核对并更新标题、正文与 tag,不创建重复 Release。随后核对 npm 包、dist-tag、远端 tag 和 Release,并跟进 Release 触发的 Doc Site 工作流至结果明确。

pnpm pub 会先运行仓库的 package-diff,再发布 ./lib。若差异检查提示缺失文件,先核对原因,不直接确认。任何发布动作失败时先记录已完成的步骤和远端状态,不盲目重试,以免重复发布。

© ant-design, MIT. 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 .agents/skills/antd-mobile-release of ant-design/ant-design-mobile.

Open the folder on GitHubat commit eee5477

Compare with similar skills

Ant Design Mobile 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.

Ant Design Mobile Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ant Design Mobile Release this skillant-design/ant-design-mobile12k—~497Automated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT
Version ReleaseNG-ZORRO/ng-zorro-antd9.2k—~3.1kAutomated safety check: PassMIT
ClawRouter Release ChecklistBlockRunAI/ClawRouter6.6k—~1.4kAutomated safety check: PassMIT

Similar skills

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

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • 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
  • 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.6k GitHub stars~3.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Version Release

    NG-ZORRO/ng-zorro-antd

    NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.

    9.2k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • 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.

    6.6k GitHub stars~1.4k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Release Clawpatch

    openclaw/clawpatch

    clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.

    813 GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

Categories

Questions about Ant Design Mobile Release

What does Ant Design Mobile Release do?

Prepares an npm release of ant-design-mobile up to the version commit, then tags and publishes the GitHub Release after you run the publish command yourself. Written in Chinese, the skill splits a release into two phases around a manual step. First the agent inspects the branch, working tree, latest master, existing tags, releases and npm versions, recommends a target version with a reason, and waits for your explicit confirmation; a stable release cannot reuse the current alpha version number, and a pre-release needs a version plus an alpha or dev tag.

When should I use Ant Design Mobile Release?

Ant Design Mobile Release fits situations like: preparing a new npm release of ant-design-mobile; tagging and creating the GitHub Release after a manual npm publish; checking npm versions, tags and releases before choosing a version number; drafting bilingual release notes covering changes since the last stable version.

How do I install Ant Design Mobile Release in Claude Code?

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

How do I install Ant Design Mobile Release in Codex?

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

Can I use Ant Design Mobile 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 ant-design/ant-design-mobile --skill antd-mobile-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/antd-mobile-release, .gemini/skills/antd-mobile-release, .github/skills/antd-mobile-release and .opencode/skills/antd-mobile-release in your project.

What does Ant Design Mobile Release need to run?

Going by SKILL.md and its folder, Ant Design Mobile Release needs the command-line tools its instructions call (pnpm and npm). Our summary lists: The ant-design-mobile repository with pnpm and npm; Permission to push to origin/master and create GitHub Releases.

Does Ant Design Mobile Release access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ant Design Mobile 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. Review the folder before installing.

What licence does Ant Design Mobile Release use?

Ant Design Mobile Release 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 Ant Design Mobile Release use?

About 497 tokens (SKILL.md is roughly 2k 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 Ant Design Mobile Release?

Skills that share tags, products or a category with Ant Design Mobile Release: ZCF Release Automation (UfoMiao/zcf, 6.1k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.6k stars) and Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ant Design Mobile Release?

ant-design (a GitHub organization) maintains it in ant-design/ant-design-mobile, which has 12,060 GitHub stars. The repository was last updated on September 14, 2026.

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