Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
准备下一个补丁版本 (Prepare next patch version release). An agent skill from open-guji/luatex-cn.
Install Prepare Next Version
$ npx skills add open-guji/luatex-cn --skill prepare-next-version -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-guji/luatex-cn prepare-next-version --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/open-guji/luatex-cn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prepare-next-version .claude/skills/prepare-next-version && 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 "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .claude/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-versionType 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 open-guji/luatex-cn --skill prepare-next-version -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-guji/luatex-cn prepare-next-version --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-guji/luatex-cn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prepare-next-version .agents/skills/prepare-next-version && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .agents/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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 open-guji/luatex-cn --skill prepare-next-version -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-guji/luatex-cn prepare-next-version --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-guji/luatex-cn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prepare-next-version .cursor/skills/prepare-next-version && 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 "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .cursor/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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/open-guji/luatex-cn.git --path .claude/skills/prepare-next-version--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 open-guji/luatex-cn --skill prepare-next-version -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-guji/luatex-cn prepare-next-version --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-guji/luatex-cn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prepare-next-version .gemini/skills/prepare-next-version && 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 "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .gemini/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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 open-guji/luatex-cn prepare-next-versionInstalls 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 open-guji/luatex-cn --skill prepare-next-version -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/open-guji/luatex-cn.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prepare-next-version .github/skills/prepare-next-version && 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 "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .github/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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 open-guji/luatex-cn --skill prepare-next-version -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install open-guji/luatex-cn prepare-next-version --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-guji/luatex-cn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prepare-next-version .opencode/skills/prepare-next-version && 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 "prepare-next-version" agent skill from https://github.com/open-guji/luatex-cn/tree/main/.claude/skills/prepare-next-version into .opencode/skills/prepare-next-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-next-version", 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
prepare-next-version- GitHub stars
- 119
- Token cost
- ~412 tokens
- SKILL.md length
- 110 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
准备下一个补丁版本 (Prepare next patch version release). An agent skill from open-guji/luatex-cn.
- Works in 6 steps: 从上一个 tag 推断版本升级类型 → 检查 VERSION 和 CHANGELOG 状态 → 如果 VERSION/CHANGELOG 未更新（情况B） → …
- Tasks that involve Changelog and release notes
- SKILL.md covers 工作流 and 后续步骤
- Calls git and python3
What it does
Prepare Next Version is an agent skill from open-guji/luatex-cn. 准备下一个补丁版本 (Prepare next patch version release)
Its SKILL.md is about 410 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. The repository describes itself as: 基于LuaTeX的中文排版宏包，支持古籍版式精确复刻，以及符合W3C《中文排版需求》的现代中文排版. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/prepare-next-version”
Requirements
- Python 3
Workflow steps
6 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 8c48bdc. 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:
gitpython3
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
Prepare Next Version loads about 412 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 110 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
The full file from open-guji/luatex-cn at commit 8c48bdc, republished under its Apache-2.0 licence (© open-guji). 110 words, ~412 tokens.
Download SKILL.mdSave it as
.claude/skills/prepare-next-version/SKILL.md (or your agent's skills folder).- name
- prepare-next-version
- description
- 准备下一个补丁版本 (Prepare next patch version release)
准备下一个版本发布工作流
本工作流用于智能地基于最后一个 git tag 推断下一个版本号，并更新所有相关文件。
工作流
1. 从上一个 tag 推断版本升级类型
# 获取最后一个 tag（格式 vX.Y.Z）
git tag -l | grep "^v" | sort -V | tail -1
# 例如：v0.2.9推断规则：
- 如果 CHANGELOG 中有新版本（大于 tag 版本），则检查升级类型
- Major 升级（0.2.9 → 0.3.0）：CHANGELOG 中出现新的 minor 版本号
- Minor 升级（0.2.8 → 0.2.9）：CHANGELOG 中只有 patch 升级
- 默认：计算补丁版本（X.Y.Z → X.Y.(Z+1)）
2. 检查 VERSION 和 CHANGELOG 状态
# 查看 VERSION 文件内容
cat VERSION
# 查看 CHANGELOG 第一个版本号
head -10 CHANGELOG.md三种情况：
| 情况 | VERSION | CHANGELOG | 操作 |
|---|---|---|---|
| A | 已更新为 0.3.0 | 已更新为 0.3.0 | 无需改动，直接更新 README |
| B | 还是 0.2.9 | 还是 0.2.9 | 执行 update_changelog，然后更新 VERSION |
| C | 0.2.9 | 0.3.0 | 异常，询问用户 |
3. 如果 VERSION/CHANGELOG 未更新（情况B）
3a. 执行 update_changelog skill
# 这会：
# - 从 git log 提取改动
# - 自动生成 CHANGELOG 条目
# - 插入新版本号和日期3b. 根据 CHANGELOG 更新 VERSION
# 读取 CHANGELOG 中的第一个版本号（跳过占位符）
# 更新 VERSION 文件为该版本号
# 例如：如果 CHANGELOG 中是 [0.3.0]
# 则 VERSION = 0.3.04. 更新 README 和 README-EN
确保 GitHub Release 链接指向当前版本：
GitHub Release: [v0.3.0](https://github.com/open-guji/luatex-cn/releases)5. 为下一个版本创建占位符
在 CHANGELOG 顶部插入新占位符：
## [X.Y.(Z+1)] - 待定
- （待填写）6. 验证更改
git diff VERSION README.md README-EN.md CHANGELOG.md后续步骤
完成版本准备后，继续使用 /release_process 技能进行完整发布流程：
- 运行单元测试：
texlua test/run_all.lua - 运行回归测试：
python3 test/regression_test.py check - 运行 l3build ctan：
l3build ctan（会自动更新所有 .sty 文件的版本号） - 提交、打标签、推送
© open-guji, Apache-2.0. 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 .claude/skills/prepare-next-version of open-guji/luatex-cn.
Open the folder on GitHubat commit 8c48bdc
Compare with similar skills
Prepare Next Version 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 |
|---|---|---|---|---|---|---|
| Prepare Next Version this skillopen-guji/luatex-cn | 119 | — | ~412 | Automated safety check: Pass | Apache-2.0 | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from open-guji/luatex-cn
All 8 skills in this repoCompare Layouts
open-guji/luatex-cn
比较 Original (ltc-guji.cls) 和 Digital (ltc-guji-digital.cls) TeX 文件的 layout 输出
Convert To Digital
open-guji/luatex-cn
将 ltc-guji.cls 文件转换为 ltc-guji-digital 格式. An agent skill from open-guji/luatex-cn.
Regression Test
open-guji/luatex-cn
运行视觉回归测试验证代码更改是否正确，支持 basic/pastissue/complete 套件及基线更新. An agent skill from open-guji/luatex-cn.
Test Tex
open-guji/luatex-cn
通过回归测试框架编译并查看 TeX 文件的渲染效果，避免在工作目录生成多余 PDF. An agent skill from open-guji/luatex-cn.
Fix GitHub Issue
open-guji/luatex-cn
修复 GitHub Issue 的完整工作流
Refactor
open-guji/luatex-cn
清理重构代码 (Code cleanup and refactoring)
Related
Categories
Questions about Prepare Next Version
What does Prepare Next Version do?
准备下一个补丁版本 (Prepare next patch version release). An agent skill from open-guji/luatex-cn. Prepare Next Version is an agent skill from open-guji/luatex-cn.
When should I use Prepare Next Version?
Prepare Next Version fits situations like: tasks that involve Changelog and release notes.
How do I install Prepare Next Version in Claude Code?
Run `npx skills add open-guji/luatex-cn --skill prepare-next-version -a claude-code`. Or copy the skill folder (.claude/skills/prepare-next-version in open-guji/luatex-cn) into .claude/skills/prepare-next-version in your project. Claude Code loads it when a task matches its description.
How do I install Prepare Next Version in Codex?
Run `npx skills add open-guji/luatex-cn --skill prepare-next-version -a codex`. Or copy the skill folder (.claude/skills/prepare-next-version in open-guji/luatex-cn) into .agents/skills/prepare-next-version in your project. Codex loads it when a task matches its description.
Can I use Prepare Next Version 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 open-guji/luatex-cn --skill prepare-next-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-next-version, .gemini/skills/prepare-next-version, .github/skills/prepare-next-version and .opencode/skills/prepare-next-version in your project.
What does Prepare Next Version need to run?
Going by SKILL.md and its folder, Prepare Next Version needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3.
Does Prepare Next Version 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 Prepare Next Version 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 Prepare Next Version use?
Prepare Next Version 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 Prepare Next Version use?
About 412 tokens (SKILL.md is roughly 1.6k 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 Prepare Next Version?
Skills that share tags, products or a category with Prepare Next Version: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prepare Next Version?
open-guji (a GitHub organization) maintains it in open-guji/luatex-cn, which has 119 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 2, 2026.
Source: open-guji/luatex-cn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.