跳到主要内容
知仓学习社ZHICANG

cull-release-prepare

Use when the user explicitly asks to prepare or bump a Cull patch, minor, or major release, curate its changelog and compatibility review, or create…

不碰外部(只输出文字)无严重或高危命中glebis/claude-skills

它会碰到什么

扫了多少2 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Cull Release Prepare

Principle

Prepare one reproducible release commit.

Preparation cannot tag, push, dispatch workflows, publish, or update Homebrew.

Required inputs

  • An explicit patch|minor|major; never infer the bump.
  • Green cull-release-check evidence bound to expectedSource and

expectedVersion.

  • Curated release notes and compatibility-review JSON matching Cull's CLI schema.

Prepare

  1. Fetch origin/main and create a dedicated clean worktree from it. Preserve

unrelated dirty worktrees.

  1. Confirm the check evidence still matches HEAD and the expected next version.
  2. Store curated notes in a safely quoted path. Use argument arrays or separately

quoted variables; never evaluate a concatenated command.

  1. Run the dry run first: npm run release:cull -- prepare ... --dry-run --json.
  2. Parse exactly one JSON envelope. Continue only when it lists exactly the

configured version, changelog, compatibility, and state files.

  1. Run the same prepare command without --dry-run.
  2. Verify one chore(release): vX.Y.Z commit, state prepared, the declared file

set, no tag, and no remote mutation.

On failure, show diagnostics and changed files. Never reset, discard, or overwrite

work outside the release-owned file set.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。