agentleFS
tandryukhatandryukha/aidemo/.claude/skills/release/SKILL.md

release

Skill32 starsChanged 7 days agoMITView on GitHub

Cut an aidemo release: bump package.json, commit, push to main — CI (release.yml) then creates the vX.Y.Z tag, moves `stable`, and publishes the GitHub Release, publishes to npm and lists the version on the MCP Registry. Use when the user says "cut a release", "release vX.Y.Z", "bump and release", "ship a new version", or "move stable". Knows the gotchas: the version lives ONLY in package.json, pushing a version bump to main IS the ship trigger, CI tagging is idempotent, npm caches the moving `stable` tag (--prefer-online to force-fresh), `npx @tandryukha/aidemo@X.Y.Z` inside this checkout doesn't run that version. Do NOT use for: installing/updating the skill in consumer repos (that's `aidemo skill update`).

  • Deletes or force-pushes
  • Installs packages
  • 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

Files
SKILL.md

release — bump + push, CI does the tagging

Your job: cut a release safely. RELEASING.md is the authoritative runbook — if it contradicts this skill, it wins. Be terse; surface only failures + final status.

Phases

  1. Preflight — clean tree, green smoke:
    git status --porcelain        # must be empty
    npm run typecheck
    For engine changes since the last tag, run the verify skill (fixture e2e) before releasing.
  2. Bump (the version lives in package.json; plugin.json and server.json mirror it) and write the release commit body = the release notes:
    npm version patch --no-git-tag-version    # or minor / major
    v=$(node -p "require('./package.json').version")
    sed -i "s/\"version\": \"[^\"]*\"/\"version\": \"$v\"/" plugins/record-demo/.claude-plugin/plugin.json server.json
    git commit -asF - <<MSG
    release: v$v
    
    - feat: what users get, one bullet per change (#issue)
    - fix: …
    MSG
    release.yml prepends that body (trailers stripped) to GitHub's generated PR list — a direct push has no PRs, so without it the notes are empty.
  3. Push — this is the ship step: once CI sees the version bump on main, the release goes out. Make sure the user actually wants a release cut (a routine end-of-session push must NOT include a version bump):
    git push origin main
  4. Watch CI do the rest — release.yml creates vX.Y.Z, moves stable, publishes the Release, npm and the MCP Registry (only when the version actually changed). Verify from outside the checkout:
    gh run watch --exit-status "$(gh run list --workflow=release.yml -L1 --json databaseId -q '.[0].databaseId')"
    gh release view "v$(node -p "require('./package.json').version")"
    (cd /tmp && npx -y "@tandryukha/aidemo@$(node -p "require('$PWD/package.json').version")" --version)
  5. Manual fallback (CI unavailable) — from RELEASING.md:
    v=vX.Y.Z
    git tag -a "$v" -m "$v" && git push origin "$v"
    git tag -f stable && git push -f origin stable
    gh release create "$v" --notes "$(git log -1 --format=%b "$v")" --generate-notes
  6. Fix notes after the fact — Actions → release → Run workflow with notes_tag: vX.Y.Z re-renders that release's notes from its commit.

Gotchas

  • CI is idempotent: an existing vX.Y.Z tag is skipped, but stable still moves and the Release is still created.
  • Inside this checkout npx @tandryukha/aidemo@<this version> installs nothing and runs the aidemo on PATH, so a stale Homebrew install prints its own version. That's not a bad release: check from another directory.
  • The release job can sit for minutes after npm publishes: the MCP Registry step waits up to 20 min for npm to serve the version. A timeout there is safe to fix with gh run rerun <id> --failed.
  • Workflow permission failures → Settings → Actions → General → Workflow permissions → Read and write.
  • Consumers on npx ...#stable may keep resolving the old commit from the npm cache right after stable moves — npx --prefer-online force-freshens; pin #vX.Y.Z for determinism.
  • Commits must be signed off (-s) like everything else in this repo (DCO).

Report

release: vX.Y.Z cut | blocked
push: done | held (not requested)
ci: tag + stable + Release verified (url) | manual fallback used | failed: <step>

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.