agentleFS
Sign inStart free
davidscotttuftsdavidscotttufts/hyvemind/skills/release/SKILL.md

release

Skill0 starsChanged 18 days agoApache-2.0View on GitHub

Cut a release: SemVer from the commits since the last tag (a data/schema migration forces at least a minor, a breaking change a major), bump the version in lockstep across every manifest, tag the merge commit's sha, then verify each registry page and that the published artifact matches the local build. Stops for user approval before tagging or publishing. Use when cutting, tagging or publishing a version.

196 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

  • 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

    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

  • 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

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before 1.0.0, a breaking change may be a minor.

    line 22
  2. Distinctive:

    Search for the old version string.

    line 28
  3. Distinctive:

    Write the changelog entry from the commits, not from memory.

    line 32
  4. Very specific:

    When upgrading the CLI version, run {{cli}} pin: it records the integrity hash and refuses releases younger than coolingOffDays.

    line 55
  5. Very specific:

    When anything went wrong, record it with the command that would have detected it (for example npm view <pkg>@<v> dist.integrity), and add …

    line 60

“Common” is measured: kept by at least 6 in 10 of the 186 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

Release

A release is the one step you can't take back: a published version is cached, mirrored and installed within minutes. Check before; prove after.

1. Decide the version from the commits

git log <last-tag>..origin/<base> --oneline (fetch first; never the local branch). Classify every commit, and state the count ("31 commits since v1.4.2"):

FoundBump at least
a breaking change to a public API, CLI, wire format or configmajor
a data or schema migration, or a new featureminor
fixes onlypatch

Before 1.0.0, a breaking change may be a minor; say so. A migration is never a patch.

2. Bump in lockstep

Find every file that carries the version: package manifests in every workspace, lockfiles, plugin/pack manifests, version constants, docs install snippets. Search for the old version string; don't rely on a list. After the bump, the same search must find the old version only in the changelog (and unrelated dependency entries).

Write the changelog entry from the commits, not from memory.

3. Tag the merged commit

The release PR merges first, through the project's own process. Then tag the merge commit's sha on the base (git tag -a vX.Y.Z <sha>), never a branch tip or your local HEAD: either can differ from what was reviewed and gated.

⛔ Show the user the version, the reasoning, the sha and the changelog entry, and wait for an explicit yes before tagging, pushing the tag, or publishing.

4. Verify after publishing

"The workflow went green" is not evidence. For each registry or package page:

  • the new version is visible to a fresh client (bypass caches);
  • the integrity hash it reports matches the artifact you meant to publish;
  • download the published artifact and compare its sha with a local build of the tagged commit. If they differ, say so and stop. Don't republish or yank without the user.

5. Upgrading hyvemind itself

When upgrading the CLI version, run {{cli}} pin: it records the integrity hash and refuses releases younger than coolingOffDays.

6. Record lessons

When anything went wrong, record it with the command that would have detected it (for example npm view <pkg>@<v> dist.integrity), and add that command to step 4 for next time.

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.

Check your setup, free