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.
为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包；按授权发布 GitHub Release，发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。
Install Package Patch Release
$ npx skills add swjybky/deepwrite --skill package-patch-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swjybky/deepwrite package-patch-release --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/swjybky/deepwrite.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/package-patch-release .claude/skills/package-patch-release && 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 "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .claude/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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 install https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-releaseType 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 swjybky/deepwrite --skill package-patch-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swjybky/deepwrite package-patch-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/package-patch-release .agents/skills/package-patch-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .agents/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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.
$ npx skills add swjybky/deepwrite --skill package-patch-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swjybky/deepwrite package-patch-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/package-patch-release .cursor/skills/package-patch-release && 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 "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .cursor/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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 https://github.com/swjybky/deepwrite.git --path .codex/skills/package-patch-release--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 swjybky/deepwrite --skill package-patch-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swjybky/deepwrite package-patch-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/package-patch-release .gemini/skills/package-patch-release && 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 "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .gemini/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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.
$ gh skill install swjybky/deepwrite package-patch-releaseInstalls 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 swjybky/deepwrite --skill package-patch-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/package-patch-release .github/skills/package-patch-release && 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 "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .github/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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.
$ npx skills add swjybky/deepwrite --skill package-patch-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swjybky/deepwrite package-patch-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/package-patch-release .opencode/skills/package-patch-release && 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 "package-patch-release" agent skill from https://github.com/swjybky/deepwrite/tree/main/.codex/skills/package-patch-release into .opencode/skills/package-patch-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-patch-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
package-patch-release- GitHub stars
- 571
- Token cost
- ~675 tokens
- SKILL.md length
- 180 words
- Files
- 2
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包；按授权发布 GitHub Release，发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。
- Works in 4 steps: 确定版本并清理 → 打包并验收 → 发布 GitHub Release → …
- Development work in your project
- SKILL.md covers 边界, 1. 确定版本并清理, 2. 打包并验收 and 3. 发布 GitHub Release, plus 1 more section
- Calls git, pnpm and gh
What it does
Package Patch Release is an agent skill from swjybky/deepwrite. 为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包；按授权发布 GitHub Release，发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development. It works with GitHub, Git and npm. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “/package-patch-release”
Workflow steps
4 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 8c49bf2. 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:
gitpnpmgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, pnpm 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Package Patch Release loads about 675 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 180 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 swjybky/deepwrite at commit 8c49bf2, republished under its Apache-2.0 licence (© swjybky). 180 words, ~675 tokens.
Download SKILL.mdSave it as
.claude/skills/package-patch-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- package-patch-release
- description
- 为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包；按授权发布 GitHub Release，发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。
打包补丁版本并按需发布
先读 测试安装包技能，命令、签名、验收及遇错修复按该技能执行；提交或推送时读 git-commit。默认只交付本地测试包，用户明确要求发布时才执行 Release 流程。
边界
- 保留工作树和暂存区已有内容，不还原、覆盖或夹带用户修改；不使用
git add .、git add -A、git commit -a、git stash、git reset、git checkout --、git clean或强推。 - 通常只改两个
package.json的版本和发布成功后的update.json；阻塞打包时允许最小修复相关代码、测试、配置及脚本，修复后继续完整打包验证。 - 本流程最终提交只能包含根目录
update.json；版本修改及故障修复留在工作树，不暂存或混入该提交。 - 对应 Release 未公开且资产未完整可下载前，不更新、提交或推送
update.json。不发布时不创建 tag、Release 或提交；要求不发 Release 却提高清单版本时说明依赖并请求决定。
1. 确定版本并清理
- 检查 Git 状态、分支、远端、两个
package.json、update.json、相关 tag/Release 及apps/desktop/release/。记录拟修改文件原内容或 diff，区分已有修改与本轮改动。 - 两个
package.json须为相同三段 SemVer；“提高一小个版本”只递增补丁位一次。用户指定版本优先，须大于基线及update.json.version。已有未完成准备时先确认并沿用本轮版本，重试不重复递增；版本不一致且无法可靠判断、或 tag/Release 属于其他发布时请求决定，不盲目覆盖。 - 仅清理
apps/desktop/release/内解析后未越界、可证明属于旧版本或本次重建目标的生成物：DeepWrite-<旧版本>-*、相应的mac/、mac-arm64/、win-unpacked/、linux-unpacked/、.icon-icns/、latest*.yml、builder-debug.yml、builder-effective-config.yaml。先列候选、再删除并核对；未知文件保留，简要说明清理结果。 - 同步修改两个顶层
version，保持其他内容和格式；暂不改update.json。
2. 打包并验收
- 从根目录执行测试安装包技能对应的
pnpm pack:test:*。失败按其修复循环继续，不停在错误报告，也不带着失败结果发布。 - 核对请求平台的安装包、更新资产和
latest*.yml非空；文件名、清单版本、引用和 SHA-512 与实际产物一致。Mac 完成 DMG、ad-hoc 签名和隔离属性检查，并记录真实冒烟结果及跨平台限制。 - 用户未授权发布时交付本地产物；已授权则继续以下流程。
3. 发布 GitHub Release
- 检查
gh auth status、远端仓库swjybky/deepwrite、tagv<新版本>和资产。禁止覆盖他人或既有公开发布；重试先读取远端状态，仅接续能确认属于本轮的 Draft，避免重复创建、重复上传。 - 先创建 Draft，标题
DeepWrite <新版本>；说明采用用户提供内容或已核实的实际变更，稳定版不标 prerelease。只上传本轮请求且验证成功的资产：Windows 为 EXE、EXE blockmap、latest.yml；Mac 为各架构 DMG、ZIP、ZIP blockmap、最终latest-mac.yml；Linux 按构建配置和实际更新清单核对。 - 两种 Mac 架构的最终清单须同时正确引用各 ZIP 与 SHA-512。缺项、上传或校验失败时保持 Draft，修复后补齐并重新核对，不能直接发布残缺自动更新。
- 用 GitHub 返回的列表核对名称、数量、非零大小，完整后发布。再次确认 tag、标题、公开状态、非 prerelease 及各下载 URL 可访问，全部通过才更新
update.json。
4. 仅提交并推送 update.json
- 保留清单其他字段语义，仅更新
version、title、与 Release 一致的releaseNotes、发布完成时 Asia/Shanghai ISO 8601publishedAt，以及https://github.com/swjybky/deepwrite/releases/tag/v<新版本>的releasePage。 - 校验 JSON 及版本与两个
package.json、tag、各latest*.yml一致。保留已有暂存区，用git commit --only -m "chore: update release manifest to v<新版本>" -- update.json限定提交。 git show --name-only --format= HEAD必须恰好只有update.json。推送前获取远端，目标分支到 HEAD 只能包含本次清单提交且可快进；否则保留成果并请求决定，不夹带其他历史。- 推送到用户指定远端/分支，未指定按发布约定用
origin/main。网络失败先核对远端 SHA 再重试，不重复提交；完成后读取远端清单确认生效。 - 报告版本、产物路径、验证结果、必要修复、Release URL 和提交 SHA，并说明版本与修复仍留在工作树。
© swjybky, 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
SKILL.md and 1 other file in .codex/skills/package-patch-release of swjybky/deepwrite.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 8c49bf2
Compare with similar skills
Package Patch 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Package Patch Release this skillswjybky/deepwrite | 571 | — | ~675 | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Deploy Docstryonlabs/opentryon | 551 | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | 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.
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.
Deploy Docs
tryonlabs/opentryon
Builds the OpenTryOn Docusaurus site in docs/, commits and pushes to the docs branch, and deploys GitHub Pages (gh-pages).
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.
Release Clawpatch
openclaw/clawpatch
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.
More from swjybky/deepwrite
Package Patch Release
swjybky/deepwrite
为 DeepWrite 桌面端递增一个 SemVer 补丁版本，安全清理上一个版本的测试打包残留，使用项目规定的 pnpm pack:test 命令构建并验证新安装包，按用户要求决定是否创建并发布 GitHub Release；Release 完整可下载后更新根目录 update.json，并通过路径限定提交和推送，保证该提交只包含…
Windows macOS Test Package
swjybky/deepwrite
构建并验证 DeepWrite Windows、macOS 测试安装包，排查打包错误、修复后继续。用于打包、测试包、Win/Mac 包及相关流程修改；版本递增和发布另用 package-patch-release。
Git Commit
swjybky/deepwrite
在 DeepWrite 创建 Git 提交、推送、Pull Request 或合并时使用，核对变更范围、项目校验、提交身份与署名。
Windows macOS Test Package
swjybky/deepwrite
按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包：使用 electron-builder 与 pnpm pack:test:，经 tools/run-test-package.mjs 编排，Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac…
Related
Categories
Questions about Package Patch Release
What does Package Patch Release do?
为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包；按授权发布 GitHub Release，发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。. Package Patch Release is an agent skill from swjybky/deepwrite.
When should I use Package Patch Release?
Package Patch Release fits situations like: development work in your project.
How do I install Package Patch Release in Claude Code?
Run `npx skills add swjybky/deepwrite --skill package-patch-release -a claude-code`. Or copy the skill folder (.codex/skills/package-patch-release in swjybky/deepwrite) into .claude/skills/package-patch-release in your project. Claude Code loads it when a task matches its description.
How do I install Package Patch Release in Codex?
Run `npx skills add swjybky/deepwrite --skill package-patch-release -a codex`. Or copy the skill folder (.codex/skills/package-patch-release in swjybky/deepwrite) into .agents/skills/package-patch-release in your project. Codex loads it when a task matches its description.
Can I use Package Patch 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 swjybky/deepwrite --skill package-patch-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/package-patch-release, .gemini/skills/package-patch-release, .github/skills/package-patch-release and .opencode/skills/package-patch-release in your project.
What does Package Patch Release need to run?
Going by SKILL.md and its folder, Package Patch Release needs the command-line tools its instructions call (git, pnpm and gh).
Does Package Patch 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 Package Patch 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 Package Patch Release use?
Package Patch Release 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 Package Patch Release use?
About 675 tokens (SKILL.md is roughly 2.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 Package Patch Release?
Skills that share tags, products or a category with Package Patch Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and Deploy Docs (tryonlabs/opentryon, 551 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Package Patch Release?
swjybky (a GitHub user) maintains it in swjybky/deepwrite, which has 571 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 4, 2026.
Source: swjybky/deepwrite on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.