agentleFS
panaversitypanaversity/ksor/.agents/skills/release/SKILL.md

release

Skill225 starsChanged 3 months agoApache-2.0View on GitHub

The release deep-workflow and runbook — how the changesets airlock works (main is releasable, never auto-released), how to test the real artifact before publishing, snapshot releases, and the diagnosis for every way the Release workflow goes red (org PR-permission, npm trusted publisher). Use when a Release run fails, when a Version Packages PR appears, when asked how/when ksor publishes, or when testing a build before release. Baseline policy lives in AGENTS.md → Changesets; this goes deeper.

  • 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, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    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. Very specific:

    NOT wasted either way — it versions and pushes changeset-release/main before dying, so the rescue is to open the PR by hand from that exact …

    line 65
  2. Distinctive:

    Never cancel a running Release.

    line 88
  3. Very specific:

    Every PR changing anything under packages/ksor needs a changeset — bundled docs included.

    line 89

“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

Releasing

The airlock — main is always releasable, never auto-released

feature PR ──CI gate + review──▶ main            nothing publishes; a changeset
                                   │             (intent file) is recorded
                                   ▼
                    "Version Packages" PR        the staging area — accumulates
                                   │             every pending changeset; can sit
                                   │             open for a month while work lands
                     a human merges it           the ONLY action that releases
                                   ▼
                    release job re-runs the      gate red = no publish
                    FULL gate, then publishes
                    with provenance (OIDC)

Release timing is controlled entirely by when the Version Packages PR is merged. Review it as a release-notes reader: the changelog it generates is what adopters will read.

Testing before publish

Three layers, all before anything reaches the registry:

  1. The PR gate — including the tarball test, which asserts the shipped bytes (dist entries, docs, LICENSE, NOTICE, CHANGELOG in the pack).
  2. A live walk of the real artifact (mandatory for CLI changes, per $implement-spec): pnpm pack in packages/ksor, install the tarball into a fresh temp dir, run the actual binary — help exit 0, unknown verb exit 1 with slug, designed verb exit 2, bundled docs present.
  3. The Version PR review — the human sign-off. Since the org toggle was enabled (2026-08-21) this PR is opened by github-actions[bot], and its CI waits for approval: the run sits in action_required with zero jobs, so gh pr checks answers "no checks reported on the 'changeset-release/main' branch". That reads like a repo with no CI and is not — approve it and the full eight-job gate runs (it passed on #48). Approve from the PR's Checks tab or with gh api -X POST repos/panaversity/ksor/actions/runs/<id>/approve, and do it before merging: after the merge the release job re-runs the whole gate anyway, but then a failure costs you a red release instead of a red PR.

To test from the registry without touching latest (only when external testers need an installable build): changesets snapshot releases — changeset version --snapshot dev && changeset publish --tag snapshot — CI only, never from a laptop. Versions look like 0.0.1-dev-20260818… and are invisible to normal npm install.

Runbook — when the Release workflow goes red

"GitHub Actions is not permitted to create or approve pull requests" (found live 2026-08-18, fixed 2026-08-21 — the owner enabled the org toggle, and the workflow opened PR #48 by itself on the first release after; every release from 0.0.7 to 0.0.11 was hand-rescued). If it returns, the toggle went back off: check gh api repos/panaversity/ksor/actions/permissions/workflow, which reports can_approve_pull_request_reviews: true when it is on. The run is NOT wasted either way — it versions and pushes changeset-release/main before dying, so the rescue is to open the PR by hand from that exact branch (gh pr create --base main --head changeset-release/main --title "Version Packages"). Permanent fix: an org admin enables the toggle (Org Settings → Actions → General → Workflow permissions); org-level blocks the repo-level one.

Publish step fails with an OIDC/auth error (E403/404): the npm Trusted Publisher is not configured. Settings on npmjs.com for @panaversity/ksor: GitHub Actions · repo panaversity/ksor · workflow release.yml · environment blank · simple publish only — leave staged publish off (nothing in the pipeline stages; grant capabilities with the machinery that uses them). The failed publish is harmless: fix the setting, re-run the failed job.

Gate step fails in the release job: main regressed after the last PR ran CI. The Version PR never triggers pull_request CI — it is opened by a bot token — which is exactly why the release job re-runs the full gate, and why this is the step that catches it. Fix on main via a normal PR, then re-run.

Hard rules (one-liners; AGENTS.md is the authority)

  • Publishing happens only in CI. Never changeset publish / npm publish from a machine — releases carry provenance or they don't ship.
  • Never cancel a running Release; the concurrency group queues.
  • Every PR changing anything under packages/ksor needs a changeset — bundled docs included. Check: pnpm changeset status --since=origin/main.

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.