with one click
release-kit
Maintainer-only release workflow skill for this repository.
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.
Menu
Maintainer-only release workflow skill for this repository.
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
Implement tasks inside an OpenSpec change. Use when the user wants to start implementation, continue implementation, or advance a change task by task. Prefer using Superpowers to refine and complete one or more unlocked tasks in the current implementation slice.
Continue an OpenSpec change by creating the next ready artifact. Use when the user wants to keep advancing proposal, specs, design, tasks, or similar artifacts without entering code implementation yet.
Enter exploration mode before or during an OpenSpec change. Use when the user wants to brainstorm first, explore options, think through requirements, compare approaches, or is not ready to move into propose/apply yet.
Use when a rough change request needs to be turned into structured OpenSpec proposal-stage artifacts such as a change proposal, RFC, architecture or design doc, spec, and task breakdown before implementation.
Generate blackbox test docs, API docs, or sync API references for OpenSpec changes. Use when a change needs documentation artifacts like blackbox-test.md, api-doc.md, or stable API reference updates.
Generate or refresh project documentation artifacts including surfaces.yaml and codemaps. Use when the user needs to initialize project docs, update codemaps after changes, or create AI-readable project overviews.
| name | release-kit |
| description | Maintainer-only release workflow skill for this repository. |
This is a maintainer-only skill entry for the in-repo release-kit/ boundary.
Use this skill only after the intended code is already merged to main.
verifypublishreleaseBefore running any mode, collect and confirm:
package.jsonDefault controlled order in v1:
verifypublishreleaseDo not continue to publish or release if the release order is not explicitly confirmed.
verifyCollect:
Delegate deterministic execution to release-kit/scripts/verify.mjs.
publishCollect:
verify -> publish -> releaseDelegate deterministic execution to release-kit/scripts/publish.mjs.
releaseCollect:
Delegate deterministic execution to release-kit/scripts/release.mjs.
release-kit/scripts/npm, git, or gh release mutations directly from the skill body