Release Cyrus

SkillAI & models

This skill handles the complete release process for the Cyrus CLI. Once added, your AI can prepare, verify, publish, and finish a coordinated release whenever you ask for one, so a new version gets out the door in order.

Available today. Use it from your connected AI after setup.

No other account needed.

Add the skill, then ask your AI to release Cyrus or publish cyrus-ai when you want a new version to go out. It will take the release through preparation, verification, publishing, and completion.

Then ask your AI: use the Release Cyrus skill

What your AI can do with it

Prepare a Cyrus CLI release
Verify everything is ready before it ships
Publish cyrus-ai as part of the release
Finish the release once it is published
Run the full /release workflow end to end

What this skill tells your AI

The instructions your AI receives, as published by cyrusagents/cyrus in skills/release/SKILL.md and read by ahel’s review.

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.

Workflow

Fetch origin/main, start from current main, and preserve unrelated local changes.
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.
- Run the F1 release test-drive protocol and save its report with the required -release-v<version>.md suffix.
- List every released package@version in CHANGELOG.md.
Run node scripts/release-packages.mjs validate <version>, then all checks required by apps/cli/RELEASING.md. Fix failures before continuing.
Commit, push, open the release PR, and merge it to main before dispatching the workflow. Never publish unmerged source or a non-main ref.
Dispatch .github/workflows/release-cli.yml from main in dry-run mode and monitor it through completion.
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.
Independently verify the version on npm and run the published CLI's --version command.
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.

Signals

GitHub stars: 802
Forks: 166
Last commit: Sep 2026
Hacker News mentions: 20

Advanced

Catalog kind: skill
Gateway key: release-cyrusagents
Source: github.com/cyrusagents/cyrus

github.com/cyrusagents/cyrus

More in AI & models

Algorithmic Art
Skill · anthropics skill-creator
Skill · anthropics interview-me
Skill · addyosmani pathfinder
Skill · thedotmack standup
Skill · thedotmack academy-guide
Skill · anthropics