mcpbeat

Cull Release Check

glebis/cull-release-check

Use when assessing whether Cull is ready to release, auditing or dry-running a Cull release, identifying version blockers, or before any Cull prepare or publish operation.

428 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
337
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/glebis/claude-skills --skill cull-release-check

What comes with it

258 bytes besides the instruction
agents/openai.yaml

The instruction itself

5 sections, as written by the author

Cull Release Check

Principle

Treat Cull's JSON release CLI as authoritative. This skill is strictly read-only.

Run the check

  • Resolve the checkout: current Git repository when its origin matches

glebis/cull; otherwise absolute CULL_REPO; otherwise

$HOME/ai_projects/cull.

  • Require an explicit patch|minor|major only when calculating a new target.

Otherwise inspect the current candidate.

  • Capture git status --porcelain and git rev-parse HEAD.
  • Run npm run release:cull -- check --bump "$KIND" --json from the checkout.
  • Parse exactly one JSON envelope from stdout. Treat extra stdout, invalid JSON,

or a nonzero exit as a blocker.

  • Capture status and HEAD again. If either changed, return

CHECK_MUTATED_REPOSITORY and stop.

Report contract

Report current and target versions, source SHA, branch and sync state, disk,

toolchains, contract gates, CI, secret presence, and every blocker. Report secret

presence only; never print environment values or secret contents.

Mutation boundary

Run no preparation, commit, tag, push, workflow dispatch, publication, Homebrew

promotion, installation, or recovery apply action. If the CLI proposes one,

report it without executing it.

How to use it

Copy the folder

Take glebis/cull-release-check from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.