agentleFS
Sign inStart free
glebisglebis/claude-skills/cull-release-publish/SKILL.md

cull-release-publish

Skill400 starsChanged 4 months agoMITView on GitHub

Use when the user explicitly asks to publish or complete a prepared Cull release, or when the authorized cull-release orchestrator reaches publication after every repository and artifact gate passes.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Create one annotated tag for the prepared commit and push that tag normally.

    line 24
  2. Distinctive:

    Never move, replace, or force-push a tag.

    line 25
  3. Very specific:

    Wait for checksum-pinned Homebrew promotion and its audit/install/launch proof.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cull Release Publish

Authority

An explicit “Release Cull patch|minor|major” or direct “Publish prepared Cull release X.Y.Z” request authorizes publication. Do not ask for another confirmation after gates pass. That authority does not waive or bypass any gate.

Implicit invocation is disabled. Without that explicit authority, stop before any tag, push, workflow dispatch, release, or tap mutation.

Publish

  1. Resolve the Cull checkout and parse one JSON envelope from npm run release:cull -- state show --version "$VERSION" --json.
  2. Require state prepared, exact metadata, a clean release commit already pushed on main, green required checks, active branch/tag protection, publication enablement, and no conflicting tag.
  3. Create one annotated tag for the prepared commit and push that tag normally. Never move, replace, or force-push a tag.
  4. Watch the tag-bound GitHub release workflow. Never substitute a local build.
  5. Require the secret-free verifier's exact artifact inventory, signatures, notarization, checksums, and provenance before automatic publication.
  6. Wait for checksum-pinned Homebrew promotion and its audit/install/launch proof.
  7. Record evidence transitions through published and homebrew-promoted using the repository CLI's state commands.

On failure, use cull-release-recover. Never delete or rewrite a tag, delete a release, replace published assets, bypass verification, or force workflow state.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free