Menu
Use only when the user explicitly requests GPT-Voice release preparation, recovery, packaging, or publishing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use only when the user explicitly requests context or rule optimization, reports stale/conflicting guidance, or requests session recovery and handoff. Keep substantial workstreams executable through focused task packets; never invoke solely because a session starts.
Use only when the user explicitly requests incremental implementation or continuation of a substantial planned workstream. Implement exactly one self-contained task packet per invocation, stop for review, and resume the next packet only after another explicit request; do not invoke merely because several files change.
Use only when the user explicitly requests an implementation plan, task decomposition, estimate, dependency map, or delivery sequence. For specification workstreams, create a compact plan index plus one separate self-contained Markdown task packet for every executable task so implementation does not preload the full specification; do not invoke automatically for routine coding.
Use only when the user explicitly requests a specification or approves a significant feature without an existing implementation contract. Define or revise durable behavior, architecture, constraints, and acceptance requirements; keep delivery order and executable task instructions out of the specification and hand decomposition to the planning workflow.
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.
| 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.