agentleFS
Sign inStart free
roee-hershroee-hersh/toolpass/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 44 days agoApache-2.0View on GitHub

Cut a toolpass release now (choose the version, check main is green, start the release workflow, verify the Python packages, image, chart and npm package). Use when asked to release, publish or tag 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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 2

    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. Distinctive:

    Use this skill for a release now, or for a minor or major bump.

    line 10
  2. Distinctive:

    If it is red or still running, fix or wait.

    line 24
  3. Very specific:

    Run the release workflow on main with version: vX.Y.Z (GitHub Actions run_workflow, or Actions → release → Run workflow).

    line 29

“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

Releasing toolpass

Releases normally happen on their own: .github/workflows/daily-release.yaml runs at 03:00 UTC and releases main as the next patch version when it changed since the last tag and CI passed on it. Use this skill for a release now, or for a minor or major bump.

1. Decide the version

  • git fetch --tags origin and list what changed since the latest vX.Y.Z tag: git log --oneline <last>..origin/main.
  • Nothing since the last tag: stop and say so.
  • While the version is 0.x: minor (0.2.0) when a user-visible feature or a breaking change landed (new command, new integration, changed config or API), patch (0.1.1) for fixes, docs and examples only. The person asking may name the version; use it.

2. Check main is releasable

  • The latest ci run on main (event push) for the head commit must be completed success. If it is red or still running, fix or wait; never release a red main.
  • A failing nightly run on main (the long property tests) is a bug to fix first, not a reason to skip.

3. Start the release

Run the release workflow on main with version: vX.Y.Z (GitHub Actions run_workflow, or Actions → release → Run workflow). For a minor or major bump you can also run daily-release with bump: minor|major, which does the checks above itself.

4. Verify

The release workflow builds everything from the tag: tag, then image, chart, assets, pypi and npm. .github/scripts/build-python.sh sets the version of toolpass (toolpass-py).

  • The run's tag, image, chart, assets, pypi and npm jobs all succeed; if one fails, read its log and fix.
  • ghcr.io/roee-hersh/toolpass:<version> and :latest exist (linux/amd64 and linux/arm64), and docker run --rm ghcr.io/roee-hersh/toolpass:<version> version prints the version.
  • helm show chart oci://ghcr.io/roee-hersh/charts/toolpass --version <version> works without logging in.
  • The pypi and npm jobs succeeded, not skipped (skipped means the PUBLISH_PYPI or PUBLISH_NPM variable is unset), and the registries serve the new version: https://pypi.org/pypi/toolpass/json and https://registry.npmjs.org/toolpass-client. The docs tell users to install from them, so a missing version is a failed release.
  • The assets job succeeded and the release lists toolpass-python.tar.gz, toolpass-client-node.tgz, the wheel toolpass-<version>-py3-none-any.whl and checksums.txt.

Reply with the release link, the version, and a short list of what it contains (PR titles).

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