agentleFS
gannonhgannonh/kata-symphony/.agents/skills/releasing-kata/SKILL.md

releasing-kata

Skill63 starsChanged 4 months agoMITView on GitHub

Releases are manually dispatched (plus scheduled Symphony nightlies). Do not bump versions in a PR to trigger a release. Root package.json version is 0.0.0 — never touch it as a release version. Nightly and stable version strings are applied by the workflow at publish time; stable finalize commits the version back to main. CLI has no nightly and no channel picker. Release math lives under scripts/release/: See release-troubleshooting.md.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. gannonh/kata★ 67100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the matching reference:

    line 35
  2. Distinctive:

    Verify tags, GitHub Releases, and npm as documented.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Kata

Releases are manually dispatched (plus scheduled Symphony nightlies). Do not bump versions in a PR to trigger a release.

TargetPackage / artifactTag formatWorkflowCoupling
Symphony + Pi extensionsymphony binary + @kata-sh/pi-symphony-extensionsymphony-vX.Y.Z and pi-symphony-vX.Y.Z (same X.Y.Z)symphony-release.ymlAlways released together
CLI@kata-sh/clicli-vX.Y.Zcli-release.ymlIndependent

Root package.json version is 0.0.0 — never touch it as a release version. Nightly and stable version strings are applied by the workflow at publish time; stable finalize commits the version back to main.

Channels

TargetChannelHowVersion
Symphony + Pistableworkflow_dispatch channel=stableExplicit version, or latest symphony-v*-nightly.* core
Symphony + PinightlySchedule every 3h on main (skips if HEAD unchanged) or channel=nightly{nextPatch}-nightly.YYYYMMDD.{run_number} from Cargo.toml patch+1
CLIsingle (manual)workflow_dispatch onlyExplicit version, or auto-bump patch from apps/cli/package.json until cli-v* is free

CLI has no nightly and no channel picker.

Version semantics

TypeWhenExample
patchBug fixes, small improvements2.3.0 → 2.3.1
minorNew features, backward compatible2.3.0 → 2.4.0
majorBreaking changes2.3.0 → 3.0.0
prereleaseValidation / alpha / beta / rc0.18.0-alpha.0 → npm tag alpha
nightlyContinuous integration builds2.3.1-nightly.20260718.42 → npm tag nightly

Workflow

  1. Identify the target (Symphony+Pi vs CLI).
  2. Read the matching reference:
    • references/symphony-release.md
    • references/cli-release.md
  3. Dispatch the workflow (optional dry_run=true first).
  4. Verify tags, GitHub Releases, and npm as documented.

Helpers

Release math lives under scripts/release/:

  • resolve-nightly-release.ts
  • resolve-stable-version.ts
  • resolve-previous-release-tag.ts
  • update-symphony-versions.ts (Cargo.toml + pi-extension package.json)
  • update-cli-version.ts

Troubleshooting

See release-troubleshooting.md.

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.