agentleFS
oliver-kriskaoliver-kriska/prmarmot/.claude/skills/cut-release/SKILL.md

cut-release

Skill10 starsChanged 40 days agoMITView on GitHub

Cut and publish a PR Marmot release end-to-end — pick the next version from the unreleased commits, bump the app and CLI versions + Cargo.lock + CHANGELOG with `make bump`, commit, and push the vX.Y.Z tag that makes CI build, sign, notarize, publish, and update the Homebrew cask; then verify the release, the cask, and the curl installer. Use this whenever asked to release, publish, ship, cut a version, tag a version, bump the version, or check a release — even if the request only says "ship it" or names a version. Do not improvise release steps from memory; this pipeline has a confirm gate and non-obvious traps (tag-only publishing, running-app SIGKILL, signed-candidate runs after packaging changes, CDN caching) that this skill encodes.

  • Deletes or force-pushes
  • Commits and pushes

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quota-axi, iterate-pr and 5 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.
  • layer5ioSkill

    quota-axi

    Report local Claude, Codex, Cursor, GitHub Copilot, and Grok quota windows via the quota-axi CLI - remaining percentages, reset times, and provider status read from local auth sources, with no routing, recommendation, or provider mutation. Use before deciding whether it is safe to keep spending a provider's quota, when the user asks about usage, rate limits, or remaining quota, or when comparing local provider headroom.

    Also in 4 projects that use this

  • SentrySkill

    iterate-pr

    Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

    Also in 4 projects that use this

  • layer5ioSkill

    gh-axi

    Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, checking CI runs, triggering workflows, cutting releases, managing Projects boards, or managing Actions secrets/variables.

    Also in 4 projects that use this

  • kunchenguidSkill

    chrome-devtools-axi

    Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.

    Also in 4 projects that use this

  • kunchenguidSkill

    lavish

    Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.

    Also in 4 projects that use this

  • RhyGSkill

    write-prd

    Also in 3 projects that use this

  • Other versions36 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 36

    1. ToolJet/ToolJet★ 41ksame name
    2. meshery/meshery★ 12ksame name
    3. danielmeppiel/apm★ 4.4ksame name
    4. microsoft/apm★ 4.4ksame name
    5. Screenly/Anthias★ 3.7ksame name
    6. Netflix/bpftop★ 2.7ksame name
    7. tansu-io/tansu★ 1.9ksame name
    8. fim-ai/fim-agent★ 1.6ksame name
    9. fim-ai/fim-one★ 1.6ksame name
    10. libredb/libredb-studio★ 1.3ksame name

    26 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

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 36 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:

    raw.githubusercontent.com caches ~5 min: after an install.sh change.

    line 44
  2. Distinctive:

    If the run fails before "Publish immutable GitHub release", nothing is public: fix on main and cut a new patch version (the tag stays …

    line 103

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

Cut a PR Marmot release

Target: github.com/oliver-kriska/prmarmot, asset prmarmot-v<X>-macos-arm64.tar.gz (Developer-ID-signed, notarized, stapled prmarmot.app, with prmarmot-cli inside), plus the cask in oliver-kriska/homebrew-tap. packaging/RELEASING.md is the source of truth; this skill is the operating procedure around it.

CI publishes, not you. Pushing an exact vX.Y.Z tag starts .github/workflows/release.yml, which runs make verify, builds, signs, notarizes, publishes the GitHub release as Latest, and updates the cask. There is no manual gh release create step and no manual-dispatch publish path.

The flow has two phases. Phase A is reversible — do it unattended. Phase B is irreversible (a pushed release commit and tag) — only start it after the user approves the version at the gate.

Traps

  • Never install over /Applications/prmarmot.app. macOS can SIGKILL a running app whose signed binary is replaced, and an instance may be under a memory measurement. Verify installs into a scratch --dir; only the user relaunches their own app. install.sh refuses while the app runs, even with --dir — say so rather than working around it.
  • Release only from an up-to-date main (git status -sb clean, equal to origin/main). The tag must point at a pushed commit.
  • CI compiles with the Rust rust-toolchain.toml pins, the same one make verify uses locally, so a green make verify means the release build compiles too. A Rust bump is its own commit before the release commit, never part of it (v0.15.0 burned on a floating stable's new -D warnings).
  • git fetch --tags first. Tags made on GitHub exist only remotely until fetched; released versions are never reused or replaced — a broken release is fixed with a new patch version.
  • Signing or packaging changed since the last tag? (scripts/sign-notarize-macos.sh, scripts/bundle-app.sh, packaging/homebrew/prmarmot.rb, .github/workflows/release*.yml) Run the publish-nothing candidate at the release commit and verify it (RELEASING.md "Safe signed candidate") before tagging. A failed notarization after the tag burns that version.
  • raw.githubusercontent.com caches ~5 min after an install.sh change.
  • A hook blocks bare git push --force; use --force-with-lease=<ref>:<expected-remote-sha> if history was rewritten.

Phase A — prepare (reversible)

1. Preflight

git fetch --tags origin && git status -sb     # clean, main == origin/main
make verify                                  # full workspace gate incl. the GPUI app (needs Metal)

2. Propose the version

git describe --tags --abbrev=0               # current, e.g. v0.6.0
make unreleased                              # what this release contains
git diff --stat "$(git describe --tags --abbrev=0)" -- scripts/sign-notarize-macos.sh \
  scripts/bundle-app.sh packaging/homebrew .github/workflows/release.yml .github/workflows/release-build.yml

Pre-1.0 heuristic: any feat: → bump minor; only fix:/chore:/deps → patch; a breaking change is the user's call. Tell the user the version and why, and wait for confirmation before touching files. If the last command printed anything, the candidate run in step 4 is required.

3. Bump (after the version is agreed)

make bump V=<X.Y.Z>     # root + cli/Cargo.toml versions, Cargo.lock, CHANGELOG.md, FEATURES.md markers; never commits
make verify
git diff --stat         # exactly Cargo.toml, cli/Cargo.toml, Cargo.lock, CHANGELOG.md (+ FEATURES.md when it had _unreleased_ markers)

4. The gate — show the user and wait

Present the version, the CHANGELOG.md diff, and whether a signed candidate is needed. If it is, the release commit must be pushed first so CI can check it out; get approval for that push, then:

gh workflow run release-build.yml --ref main -f ref=<full-release-commit-sha>
gh run watch <run-id> --exit-status

and verify the downloaded candidate per RELEASING.md (including the prmarmot-cli signature lines). Get explicit approval for the tag.

Phase B — publish (irreversible, only after approval)

git add Cargo.toml cli/Cargo.toml Cargo.lock CHANGELOG.md FEATURES.md
git commit -m "chore(release): v<X.Y.Z>"     # cliff.toml skips this commit next cycle
git push origin main
git tag v<X.Y.Z> && git push origin v<X.Y.Z>
gh run list --workflow release.yml --limit 1 # then: gh run watch <run-id> --exit-status

If the run fails before "Publish immutable GitHub release", nothing is public: fix on main and cut a new patch version (the tag stays burned). If tap publication fails after the release exists, do not rerun the workflow; run scripts/update-homebrew-cask.sh from a trusted checkout.

Verify end-to-end

gh api repos/oliver-kriska/prmarmot/releases/latest --jq .tag_name     # v<X.Y.Z>
gh api repos/oliver-kriska/homebrew-tap/contents/Casks/prmarmot.rb --jq .content | base64 -d | grep -E 'version|sha256'

With the user's app quit (ask; never quit it yourself), test the README installer into scratch directories:

curl -fsSL https://raw.githubusercontent.com/oliver-kriska/prmarmot/main/install.sh \
  | sh -s -- --dir "$SCRATCHPAD/install-test" --bin-dir "$SCRATCHPAD/install-bin" --repo oliver-kriska/prmarmot
codesign --verify --deep --strict "$SCRATCHPAD/install-test/prmarmot.app"
spctl --assess --type execute "$SCRATCHPAD/install-test/prmarmot.app"
"$SCRATCHPAD/install-bin/prmarmot-cli" --version                       # prmarmot-cli <X.Y.Z>

unreleased.yml clears the draft "Unreleased" release on the tag push — confirm it is gone. Tell the user to brew upgrade --cask prmarmot or rerun the installer and relaunch; never swap their running app for them.

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.