菜单
Release staged changes in Virgulas: run cache-busting scripts, branch, commit with Conventional Commits, push, and open a PR. Use when the user asks to create a release, ship changes, or publish staged work.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pitermarx/Virgulas --skill release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | release |
| description | Release staged changes in Virgulas: run cache-busting scripts, branch, commit with Conventional Commits, push, and open a PR. Use when the user asks to create a release, ship changes, or publish staged work. |
| argument-hint | optional: describe the changes to include in the PR description |
Before branching, determine what changed:
| Changed files | Script to run |
|---|---|
source/vendor/ | npm run vendor:sync then npm run sw:bump |
source/css/, source/js/, source/index.html, source/fonts/, source/media/ | npm run sw:bump |
| Nothing in the above groups | No script needed |
Run npm run sw:bump whenever any app or vendor file changes. It is idempotent and safe to run even when nothing changed — it will report "nothing bumped".
git diff --staged
Understand what changed to write the commit message and decide which scripts to run.
If vendor files changed:
npm run vendor:sync
npm run sw:bump
If only app/font/media files changed:
npm run sw:bump
Then stage any files modified by these scripts:
git add source/sw.js scripts/.sw-cache-hashes.json
# if vendor:sync ran, also:
git add source/vendor/
Name it after the primary type and scope of the change, following the repo's branch naming convention:
feat/<short-slug>
fix/<short-slug>
chore/<short-slug>
git checkout -b feat/<slug>
The staged index travels with the checkout — no need to stash.
Use Conventional Commits:
type(scope)!: subject
feat, fix, perf, refactor, revert, chore, style, docs, test! after scopegit commit -m "feat(ui): short summary
- Detail 1
- Detail 2
- Bump APP_CACHE vN → vN+1"
git push -u origin <branch-name>
gh pr create \
--title "<same as commit subject>" \
--body "## Changes\n\n- ...\n- ..." \
--base main \
--head <branch-name>
npm run sw:bump is automatically called by npm install (postinstall), so vendor bumps are hands-off when dependencies change.pre-push Git hook (if installed via npm run sw:hooks) also runs sw:bump and aborts if sw.js was modified but not committed.sw:bump — stale caches will serve outdated app files to users.vendor:sync is only needed when a dependency version changes in package.json (it copies CDN-resolved bundles into source/vendor/).