agentleFS
alexnodelandalexnodeland/hoist/.claude/skills/release/SKILL.md

release

Skill2 starsChanged 33 days agoMITView on GitHub

Cut a Hoist release as docs/releasing.md describes, covering the version bump, the CHANGELOG section, the dry run, the vX.Y.Z tag, what release.yml and container.yml then publish, and the checks after. Use when the owner asks to prepare, dry-run or cut a release, or asks how releases work. Tagging and publishing wait for the owner's explicit go-ahead.

  • Pipes a download into a shell
  • Commits and pushes

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Run by hand with dry_run checked (the default), it builds and packages everything, uploads it as the artifact release, and publishes …

    line 17
  2. Distinctive:

    The version: Before 1.0, bump the minor version for a change a user must act on, such as a flow format this version no longer reads, and …

    line 23

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “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

Releasing Hoist

docs/releasing.md is the procedure; read it first, since it is the source of truth and this skill is a summary. A version tag starts workflows that publish, so tagging, pushing a tag and running Release with dry_run unchecked are for the owner to decide. Prepare everything up to that point, and ask.

What the workflows do

  • release.yml, on a v* tag or by hand from the Actions tab:
    • notes checks that the tag is v plus the version in Cargo.toml, and takes the notes from CHANGELOG.md's ## X.Y.Z section, rewriting relative links to the tag. It fails before any build if either is wrong.
    • ui builds the console's UI (console/dist) once.
    • build makes a --locked --release build of the five binaries (hoist, hoist-mcp, hoist-procedure, hoist-mcp-demo, and hoist-console with the UI built in; it fails without console/dist) for five targets, runs each binary's --version where the runner can, and packs an archive with LICENSE and README.md.
    • release writes SHA256SUMS, copies install.sh and install.ps1, fills the Homebrew formula (packaging/homebrew/fill.sh), and creates the GitHub release once every build has passed. A tag with a hyphen (v0.2.0-rc.1) makes a pre-release.
    • Run by hand with dry_run checked (the default), it builds and packages everything, uploads it as the artifact release, and publishes nothing. Unchecked, it tags the commit v<version> itself and then starts container.yml on the tag.
  • container.yml, on the same tag, publishes two images for linux/amd64 and linux/arm64, tagged X.Y.Z, X.Y and latest: ghcr.io/alexnodeland/hoist, the CLI, and ghcr.io/alexnodeland/hoist-console, the console (the Dockerfile's console target). The arm64 builds, under QEMU, are the slowest steps.
  • Nothing goes to crates.io (docs/releasing.md, "crates.io", says why). Never run cargo publish.

Prepare a release

  1. The version. Before 1.0, bump the minor version for a change a user must act on, such as a flow format this version no longer reads, and the patch version otherwise.
  2. Bump it. Set version in [workspace.package] in the root Cargo.toml; every crate inherits it. cargo build updates Cargo.lock. Then make ci.
  3. The changelog. In CHANGELOG.md, turn ## Unreleased into ## X.Y.Z (YYYY-MM-DD) and start an empty ## Unreleased above it. The notes are the lines under that heading, up to the next ## .
  4. The lines that name a version in README.md and docs/install.md: grep -n 'v0\.\|0\.[0-9]\.[0-9]' README.md docs/install.md.
  5. A dry run: the owner runs Release by hand with dry_run checked. A macOS or Windows build failure shows up there, before any tag exists.
  6. Merge to main with CI green, through a pull request.

Cut it (the owner's go-ahead first)

git switch main && git pull
git tag -a vX.Y.Z -m "Hoist X.Y.Z"
git push origin vX.Y.Z

The project settings ask before git push of a tag and before gh release.

After

  • The release page lists five archives, SHA256SUMS, install.sh, install.ps1 and hoist.rb.
  • curl -fsSL https://github.com/alexnodeland/hoist/releases/latest/download/install.sh | sh -s -- --prefix /tmp/hoist-check, then /tmp/hoist-check/bin/hoist doctor.
  • docker run --rm ghcr.io/alexnodeland/hoist:X.Y.Z --version, and the same for ghcr.io/alexnodeland/hoist-console:X.Y.Z.
  • The console from the archive serves its UI: start /tmp/hoist-check/bin/hoist-console, and the URL it prints shows the app, not the page saying how to build one.
  • The Homebrew tap, if it exists: copy the release's hoist.rb to Formula/hoist.rb there (docs/releasing.md, "Homebrew").

When a build fails: fix it on main, delete the tag (git push --delete origin vX.Y.Z, git tag -d vX.Y.Z) and tag the fixed commit. The next image publish replaces the tags an earlier one wrote.

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.