glebis/claude-skills

cull-release-recover

Use when a Cull release is stuck, inconsistent, failed in a workflow or artifact gate, missing Homebrew promotion, failed after publication, or needs a safe recovery or patch plan.

First seen Jul 15, 2026

Installation

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from glebis/claude-skills · top by installs.

npx skills add glebis/claude-skills

Browse all from glebis/claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 372
License MIT
Default branch main
Open issues 6
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,531 B
  • docs SUMMARY.md 208 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 21 installs

SKILL.md

Cull Release Recover

Principle

Derive truth from external evidence, then resume the first incomplete safe phase. Never erase immutable release history to make local state look consistent.

Diagnose

  1. Resolve the Cull checkout.
  2. Run npm run release:cull -- resume --version "$VERSION" --json and parse

exactly one JSON envelope. Treat local release state as a cache.

  1. Authenticate and compare the prepared commit, remote annotated tag and peeled

commit, Actions run, exact asset inventory, public release, updater metadata, provenance, and Homebrew cask/evidence.

  1. Classify the next action exactly as rerun-check, prepare-new-version,

watch-build, verify-artifact, publish-verified-artifacts, promote-homebrew, or prepare-patch-plan.

  1. Execute only the safe resumable phase the user already authorized. Do not

repeat a completed signed build or replace verified artifacts.

A post-publish verification failure creates or updates the stable P0 bd incident, blocks later release checks, and returns prepare-patch-plan. Prepare the patch plan but never publish that patch implicitly.

Never delete or move a tag or release. Never force-push, clobber assets, reset unrelated work, bypass a gate, clean cull.db, or treat missing evidence as success.