agentleFS
matteoepitechmatteoepitech/tonton-claude/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 18 days agoMITView on GitHub

Checklist for cutting a Tonton Claude release (app DMG, agents, relay, install scripts) from a signed version tag. Maintainer only.

  • 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

  • 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 183 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:

    Only the maintainer tags. An agent prepares, checks and writes the commands.

    line 9
  2. Distinctive:

    Look for anything that needs an order of updates:

    line 17
  3. Very specific:

    If the relay changed, update the hosted relay with install-relay.sh (see docs/self-hosting.md).

    line 46

“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

Cutting a release

Only the maintainer tags. An agent prepares, checks and writes the commands; the maintainer runs them, because the tag is signed with their key.

Before the tag

  1. main is green on CI: gh run list --branch main --workflow ci.yml -L 1.
  2. Pick the version from the changes since the last tag (git log $(git describe --tags --abbrev=0)..main --oneline): a new feature bumps the minor, fixes only bump the patch.
  3. Look for anything that needs an order of updates:
    • relay/ changed: self-hosters must update the relay. Does the new app still work with the previous relay?
    • shared/protocol.ts changed: see the version table in the protocol-change skill.
    • The agent changed: users get Update agent in the app; agents older than 0.4.0 need the install command again.
  4. Draft the release notes: what users see, then what self-hosters must do.
  5. App updates: gh variable list shows SPARKLE_PUBLIC_KEY and gh secret list shows SPARKLE_PRIVATE_KEY. Without both, the release ships without an appcast.xml and that version of the app never updates itself; with only one, the workflow stops. Setting them up once is in docs/self-hosting.md (Releasing). Never replace the key pair: installed apps only accept updates signed with the key they were built with.

Tag

git switch main && git pull --ff-only
git tag -s vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z

.github/workflows/release.yml then publishes the DMG, the agents, the relay executables and Docker image, the install scripts and SHA256SUMS.

After

  • The workflow is green and the release has every asset listed in the workflow, appcast.xml included.
  • On a Mac running the previous version (one built with the update keys), Settings › General › Check for Updates… offers the new one and installs it.
  • Install the DMG on a Mac and check that Update agent appears for a machine on the previous version.
  • With a Developer ID, the widget is in the gallery (right-click the desktop › Edit Widgets…, search Tonton) once the new app has started, and it lists the sessions of the notch. Ad-hoc releases have no widget.
  • If the relay changed, update the hosted relay with install-relay.sh (see docs/self-hosting.md).
  • Point the Nix flake at the new release: bun scripts/nix-release.ts, then commit nix/release.json on a branch and open a PR (docs/nix.md). Until then, Nix users get the previous version.

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.