Skip to content
alyn
glebis

Cull Release Check skill

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.

$npx skills add glebis/claude-skills --skill cull-release-check
View this skill on GitHubglebis/claude-skills/cull-release-check/SKILL.md
Pack stars
413
Pack installs
15k
Alyn Score
53/99
Updated
8 h ago
License
MIT
– views – installs via Alyn
DevOps

Install Cull Release Check

Pick your agent. Every command is ready to paste.

$npx skills add glebis/claude-skills --skill cull-release-check

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads cull-release-check when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the cull-release-check skill”. In Codex, type $cull-release-check.

The skill itself

SKILL.md

FolderGitHub

Cull Release Check

Principle

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

Run the check

  1. Resolve the checkout: current Git repository when its origin matches glebis/cull; otherwise absolute CULL_REPO; otherwise $HOME/ai_projects/cull.
  2. Require an explicit patch|minor|major only when calculating a new target. Otherwise inspect the current candidate.
  3. Capture git status --porcelain and git rev-parse HEAD.
  4. Run npm run release:cull -- check --bump "$KIND" --json from the checkout.
  5. Parse exactly one JSON envelope from stdout. Treat extra stdout, invalid JSON, or a nonzero exit as a blocker.
  6. Capture status and HEAD again. If either changed, return CHECK_MUTATED_REPOSITORY and stop.

Before reporting green, sanity-check the two blockers that recur between releases: free disk (delete regenerable target/ dirs — gates need ≥15 GiB and targets regrow 7–11 GB per build) and the dependabot auto-merge queue (it can advance main between check and tag; wait for it to drain or account for it).

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.

Tips for Cull Release Check

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Cull Release Check

What does the Cull Release Check skill do?

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.

How do I install Cull Release Check?

Run "npx skills add glebis/claude-skills --skill cull-release-check" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Cull Release Check work in Cursor and Codex?

Yes. Cull Release Check uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Cull Release Check free?

Cull Release Check is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Cull Release Check?

Cull Release Check is published by glebis in the glebis/claude-skills repository, together with 29 other skills.

Similar skills. From other creators.