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.
准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送. An agent skill from limecloud/lime.
Install Lime Release Workflow
$ npx skills add limecloud/lime --skill lime-release-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install limecloud/lime lime-release-workflow --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/limecloud/lime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/lime-release-workflow .claude/skills/lime-release-workflow && 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 "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .claude/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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/limecloud/lime/tree/main/.codex/skills/lime-release-workflowType 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 limecloud/lime --skill lime-release-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install limecloud/lime lime-release-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/limecloud/lime.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/lime-release-workflow .agents/skills/lime-release-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .agents/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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 limecloud/lime --skill lime-release-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install limecloud/lime lime-release-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/limecloud/lime.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/lime-release-workflow .cursor/skills/lime-release-workflow && 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 "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .cursor/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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/limecloud/lime.git --path .codex/skills/lime-release-workflow--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 limecloud/lime --skill lime-release-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install limecloud/lime lime-release-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/limecloud/lime.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/lime-release-workflow .gemini/skills/lime-release-workflow && 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 "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .gemini/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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 limecloud/lime lime-release-workflowInstalls 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 limecloud/lime --skill lime-release-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/limecloud/lime.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/lime-release-workflow .github/skills/lime-release-workflow && 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 "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .github/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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 limecloud/lime --skill lime-release-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install limecloud/lime lime-release-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/limecloud/lime.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/lime-release-workflow .opencode/skills/lime-release-workflow && 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 "lime-release-workflow" agent skill from https://github.com/limecloud/lime/tree/main/.codex/skills/lime-release-workflow into .opencode/skills/lime-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lime-release-workflow", 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
lime-release-workflow- GitHub stars
- 1.5k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 567 words
- Files
- 1
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- None found
At a glance
准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送. An agent skill from limecloud/lime.
- Works in 3 steps: 明确目标版本。 → 检查现状。 → 如果发现上一轮发版命令仍在跑，只停止自己启动且已被用户中断的进程；不杀掉明显属于用…
- Tasks that involve Changelog and release notes
- SKILL.md covers 核心原则, 入口判断, Release Candidate 范围确认 and 更新版本事实源, plus 5 more sections
- Calls git, npm and cargo
What it does
Lime Release Workflow is an agent skill from limecloud/lime. 准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送。
Its SKILL.md is about 1.8k 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 Changelog and release notes. It works with npm, Git and Rust. The repository describes itself as: Full-stack AI agent for coding, files, terminals, tools, research, content, multimodal work, and multi-agent workflows.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/lime-release-workflow”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- 明确目标版本。
- 检查现状。
- 如果发现上一轮发版命令仍在跑，只停止自己启动且已被用户中断的进程；不杀掉明显属于用户的 dev server / test / Electron 进程。
What it can do on your machine
Read from SKILL.md and the folder at commit 1236c5e. 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:
gitnpmcargonpxnoderg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and npx, 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
Lime Release Workflow loads about 1.8k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 567 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 567 words (~1,843 tokens).
- name
- lime-release-workflow
Files
Just SKILL.md in .codex/skills/lime-release-workflow of limecloud/lime.
Open the folder on GitHubat commit 1236c5e
Compare with similar skills
Lime Release Workflow 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 |
|---|---|---|---|---|---|---|
| Lime Release Workflow this skilllimecloud/lime | 1.5k | — | ~1.8k | Automated safety check: Pass | None | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 8.9k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Releasexin2017338/lynx-proxy | 502 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
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.
Release
xin2017338/lynx-proxy
Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.
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.
More from limecloud/lime
All 18 skills in this repoPersonal Ip Knowledge Builder
limecloud/lime
将访谈稿、聊天记录、简历、公开内容、业务资料、案例和既有 DOCX/Markdown 文档，提炼成可被 AI 长期调用的个人 IP 知识库。适用于用户要求“生成个人知识库”“整理成个人 IP 成品知识库”“为创始人/专家/讲师/主播/顾问建立AI知识库”“把资料变成个人IP底层提示词/写作风格库/故事素材库/话术库”的场景。
Brand Persona Knowledge Builder
limecloud/lime
将品牌定位、价值观、受众画像、语气风格、内容样例、危机回应和表达禁区，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的品牌人设知识库。适用于用户要求“整理品牌人设”“沉淀品牌口吻”“把品牌资料变成可复用语气库”“维护品牌 persona pack”的场景。
Brand Product Knowledge Builder
limecloud/lime
将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的产品资料知识库。适用于用户要求“整理产品知识库”“沉淀产品 FAQ”“把品牌产品资料变成项目资料”“维护产品资料包”的场景。
Campaign Operations Knowledge Builder
limecloud/lime
将活动目标、用户路径、渠道分工、物料资产、时间节奏、风险预案和复盘结论等资料，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的运营类知识库。适用于用户要求“整理活动 / Campaign 运营知识库”“沉淀运营 SOP”“把运营资料变成项目资料”“维护运营知识库”的场景。
Content Operations Knowledge Builder
limecloud/lime
将选题日历、栏目矩阵、素材资产、发布节奏、复盘结论和内容边界等资料，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的运营类知识库。适用于用户要求“整理内容运营知识库”“沉淀运营 SOP”“把运营资料变成项目资料”“维护运营知识库”的场景。
Growth Strategy Knowledge Builder
limecloud/lime
将增长目标、指标体系、渠道策略、实验计划、复盘结论、资源约束和停止条件，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的增长策略知识库。适用于用户要求“整理增长知识库”“沉淀增长策略”“把增长计划变成项目资料”“维护增长实验资料包”的场景。
Related
Categories
Questions about Lime Release Workflow
What does Lime Release Workflow do?
准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送. An agent skill from limecloud/lime. Lime Release Workflow is an agent skill from limecloud/lime.
When should I use Lime Release Workflow?
Lime Release Workflow fits situations like: tasks that involve Changelog and release notes.
How do I install Lime Release Workflow in Claude Code?
Run `npx skills add limecloud/lime --skill lime-release-workflow -a claude-code`. Or copy the skill folder (.codex/skills/lime-release-workflow in limecloud/lime) into .claude/skills/lime-release-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Lime Release Workflow in Codex?
Run `npx skills add limecloud/lime --skill lime-release-workflow -a codex`. Or copy the skill folder (.codex/skills/lime-release-workflow in limecloud/lime) into .agents/skills/lime-release-workflow in your project. Codex loads it when a task matches its description.
Can I use Lime Release Workflow 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 limecloud/lime --skill lime-release-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lime-release-workflow, .gemini/skills/lime-release-workflow, .github/skills/lime-release-workflow and .opencode/skills/lime-release-workflow in your project.
What does Lime Release Workflow need to run?
Going by SKILL.md and its folder, Lime Release Workflow needs the command-line tools its instructions call (git, npm, cargo, npx, node and rg). Our summary lists: Node.js.
Does Lime Release Workflow access the network?
SKILL.md contains no URLs. Its commands use git, npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Lime Release Workflow 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 Lime Release Workflow use?
No licence was found for Lime Release Workflow or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Lime Release Workflow use?
About 1.8k tokens (SKILL.md is roughly 7.4k 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 Lime Release Workflow?
Skills that share tags, products or a category with Lime Release Workflow: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars) and Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lime Release Workflow?
limecloud (a GitHub organization) maintains it in limecloud/lime, which has 1,485 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 5, 2026.
Source: limecloud/lime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.