一键在 Manus 中运行任何 Skill

开始使用

release-kit

星标21

分支6

更新时间2026年4月11日 16:14

Maintainer-only release workflow skill for this repository.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

chhuax

chhuax/praxis-devos

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

release-kit

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.

Modes

verify / publish / release
verify
publish
release

Input collection rules

Before running any mode, collect and confirm:

target version from package.json
explicit release order confirmation
whether the user wants the normal path or a compensation path

Default controlled order in v1:

verify
publish
release

Do not continue to publish or release if the release order is not explicitly confirmed.

Mode responsibilities

`verify`

Collect:

target version
current repository root / worktree context
confirmation that the user wants to prepare the release candidate

Delegate deterministic execution to release-kit/scripts/verify.mjs.

`publish`

Collect:

target version
confirmation that verified state already exists and is still valid
confirmation that the approved order is verify -> publish -> release

Delegate deterministic execution to release-kit/scripts/publish.mjs.

`release`

Collect:

target version
confirmation that publish/tag already completed, or that the user wants the compensation path
confirmation that GitHub Release creation is intended now

Delegate deterministic execution to release-kit/scripts/release.mjs.

Responsibilities

Collect the target version and release-order confirmation
Keep the execution flow constrained to the approved release workflow
Delegate all deterministic execution to repo scripts under release-kit/scripts/
Route normal and compensation paths without embedding release logic here

Constraints

Supports Node/npm + git + GitHub only in v1
Not part of the projection system
Must not implement high-risk release commands directly in this file
Must not replace explicit user confirmation for release order
Must not perform npm, git, or gh release mutations directly from the skill body

同仓库更多 Skills

同仓库

openspec-apply-change

chhuax/praxis-devos

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.

2026-04-2521

openspec-continue-change

chhuax/praxis-devos

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.

2026-04-2521

openspec-explore

chhuax/praxis-devos

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.

2026-04-2521

openspec-propose

chhuax/praxis-devos

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.

2026-04-2521

devos-change-docs

chhuax/praxis-devos

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.

2026-04-1921

devos-docs

chhuax/praxis-devos

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.

2026-04-1921

name	release-kit
description	Maintainer-only release workflow skill for this repository.

release-kit

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.

Modes

verify / publish / release
verify
publish
release

Input collection rules

Before running any mode, collect and confirm:

target version from package.json
explicit release order confirmation
whether the user wants the normal path or a compensation path

Default controlled order in v1:

verify
publish
release

Do not continue to publish or release if the release order is not explicitly confirmed.

Mode responsibilities

`verify`

Collect:

target version
current repository root / worktree context
confirmation that the user wants to prepare the release candidate

Delegate deterministic execution to release-kit/scripts/verify.mjs.

`publish`

Collect:

target version
confirmation that verified state already exists and is still valid
confirmation that the approved order is verify -> publish -> release

Delegate deterministic execution to release-kit/scripts/publish.mjs.

`release`

Collect:

target version
confirmation that publish/tag already completed, or that the user wants the compensation path
confirmation that GitHub Release creation is intended now

Delegate deterministic execution to release-kit/scripts/release.mjs.

Responsibilities

Collect the target version and release-order confirmation
Keep the execution flow constrained to the approved release workflow
Delegate all deterministic execution to repo scripts under release-kit/scripts/
Route normal and compensation paths without embedding release logic here

Constraints

Supports Node/npm + git + GitHub only in v1
Not part of the projection system
Must not implement high-risk release commands directly in this file
Must not replace explicit user confirmation for release order
Must not perform npm, git, or gh release mutations directly from the skill body