agentleFS
cyrusagentscyrusagents/cyrus/skills/release/SKILL.md

release

Skill902 starsChanged 53 days agoApache-2.0View on GitHub

Prepare, verify, publish, and finish a coordinated Cyrus CLI release. Use when a user asks to release Cyrus, publish cyrus-ai, run a CLI release, or perform the /release workflow.

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

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 182 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run Cyrus releases through the trusted-publishing workflow.

    line 8
  2. Very specific:

    Read apps/cli/RELEASING.md completely before taking release actions.

    line 13
  3. Very specific:

    Run pnpm install and commit any lockfile change.

    line 29
  4. Very specific:

    Run node scripts/release-packages.mjs validate <version>, then all checks required by apps/cli/RELEASING.md.

    line 37
  5. Distinctive:

    Commit, push, open the release PR, and merge it to main before dispatching the workflow.

    line 39
  6. Very specific:

    Only when the user has explicitly requested the live release, dispatch the same exact version with dry_run=false.

    line 43
  7. Very specific:

    Use the Linear integration to move every issue referenced by the version's changelog section from MergedUnreleased to ReleasedMonitoring.

    line 48
  8. Distinctive:

    Never add an npm token. Publishing must use GitHub Actions OIDC.

    line 53
  9. Distinctive:

    Never rerun a partially published version blindly.

    line 57
  10. Distinctive:

    Do not create or move a release tag until every package is published.

    line 59

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

Release Cyrus

Run Cyrus releases through the trusted-publishing workflow. Do not publish workspace packages manually.

Required reference

Read apps/cli/RELEASING.md completely before taking release actions. Treat it as the canonical operator guide and scripts/release-packages.mjs as the canonical package list and dependency order.

Editing release workflows, scripts, installers, or release documentation does not invoke this release procedure. Validate those changes with targeted checks and the F1 applicability policy in skills/f1-test-drive/SKILL.md.

Workflow

  1. Fetch origin/main, start from current main, and preserve unrelated local changes.
  2. Prepare the release on a branch:
    • Move both changelogs' Unreleased entries into the new version.
    • Set the same version in every manifest printed by node scripts/release-packages.mjs list.
    • Run pnpm install and commit any lockfile change.
    • Assess the entire payload since the previous release using the canonical F1 applicability policy, including functional changes merged before the version-bump PR. For F1-covered behavior changes, run relevant F1 scenarios and save evidence with the required -release-v<version>.md suffix. Otherwise record the payload assessment and targeted checks as non-F1 release verification per apps/cli/RELEASING.md; do not invent an F1 report.
    • List every released package@version in CHANGELOG.md.
  3. Run node scripts/release-packages.mjs validate <version>, then all checks required by apps/cli/RELEASING.md. Fix failures before continuing.
  4. Commit, push, open the release PR, and merge it to main before dispatching the workflow. Never publish unmerged source or a non-main ref.
  5. Dispatch .github/workflows/release-cli.yml from main in dry-run mode and monitor it through completion.
  6. Only when the user has explicitly requested the live release, dispatch the same exact version with dry_run=false. Monitor it through npm publication, git tagging, and GitHub Release creation.
  7. Independently verify the version on npm and run the published CLI's --version command.
  8. Use the Linear integration to move every issue referenced by the version's changelog section from MergedUnreleased to ReleasedMonitoring.

Safety

  • Never add an npm token. Publishing must use GitHub Actions OIDC.
  • Confirm every npm package trusts cyrusagents/cyrus and release-cli.yml before the first live workflow run.
  • A dry run does not authenticate to npm and does not prove registry writes.
  • Never rerun a partially published version blindly. npm versions are immutable; inspect which packages landed and recover deliberately.
  • Do not create or move a release tag until every package is published. The workflow owns tag and GitHub Release creation.

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.