agentleFS
dosu-aidosu-ai/decant/.claude/skills/decant-release/SKILL.md

decant-release

Skill75 starsChanged 5 days agoApache-2.0View on GitHub

Cut a Decant release (signed vX.Y.Z tag that triggers the release workflow for GitHub Releases, npm, GHCR, and the Homebrew tap). Use when asked to release, tag, or publish Decant, or to check whether main is ready to release.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    Follow "Verify a release" in docs/distribution.md (checksums, gh attestation verify, npm audit signatures) and report the results.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Release Decant

Publishing is irreversible: npm versions cannot be reused and the Homebrew tap updates for every user.

Stop and ask the user for explicit approval before running just release, pushing any tag, dispatching release.yml, merging with --admin, or re-running a release job. An earlier approval in the same conversation does not cover a new tag.

Preflight

  1. On main (or a pushed release/* branch for a backport), clean tree, up to date with its origin branch.
  2. just check passes locally (needs network for the npm pack smoke).
  3. CI is green on the exact commit you will tag.
  4. Pick the version: semver without a leading v. Prerelease suffixes such as -beta.1 and backport tags below the newest release publish to narrower channels; docs/distribution.md describes which.

Tag

just release VERSION re-checks step 1 of the preflight only, then creates a signed annotated tag vVERSION and pushes it, so the approval above must come first. Signing is required; do not bypass it.

What the tag triggers

.github/workflows/release.yml refuses a tag whose commit is not on main or a release/* branch. It builds the platform binaries (codesigned when signing secrets are configured), attests them, publishes GitHub Release assets with SHA256SUMS, publishes the npm launcher and platform packages with provenance, pushes the GHCR image, and updates the formula in dosu-ai/homebrew-dosu. Each publishing job waits for approval in the release environment. Approving those deployments is the user's call, the same as pushing the tag.

Afterwards

Follow "Verify a release" in docs/distribution.md (checksums, gh attestation verify, npm audit signatures) and report the results. If a job fails, report the failing step and wait for the user before re-running or retagging.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.