菜单
Use only when the user explicitly requests GPT-Voice release preparation, recovery, packaging, or publishing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use only when the user requests a code review or a dedicated pre-merge review; do not add it automatically after implementation.
Use only when the user explicitly requests simplification or a behavior-preserving clarity refactor.
Use only when the user requests context/rule optimization or an explicit session-recovery and handoff task; never use solely because a session starts.
Use only when the user explicitly requests documentation, an ADR, or an architecture-decision record; not for routine implementation notes.
Use only when the user explicitly requests adversarial review or a named high-risk decision needs an independent challenge; never for every unfamiliar task.
Use only when the user explicitly asks to ideate, refine an idea, or stress-test a plan before committing to it.
| name | project-release |
| description | Use only when the user explicitly requests GPT-Voice release preparation, recovery, packaging, or publishing. |
Use this workflow only for a confirmed vMAJOR.MINOR.PATCH release target. Do not change the app version without an explicit user request.
main.Run the standard PR checks, then the affected packaging checks:
npm run prepare:cloakbrowser
npm run smoke:cloakbrowser
npm run generate:package-metadata
npm run pack
npm run verify:packaged
For release artifacts, use the matching target command. Linux releases should prefer the reproducible Fedora path:
npm run dist:fedora
Windows and macOS require their corresponding supported environments. macOS packaging remains blocked until signing and notarization are configured.
project-pull-request.vMAJOR.MINOR.PATCH tag from the merged main commit.Never commit release artifacts, local app data, session files, logs, browser profiles, or credentials. Treat signed artifacts and release credentials as sensitive. If any artifact has already been published with a defect, publish a follow-up patch rather than moving or replacing the release tag.