release
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.
- Installs
- 831
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cyrusagents/cyrus --skill release- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads release automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- 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 installand 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>.mdsuffix. Otherwise record the payload assessment and targeted checks as non-F1 release verification perapps/cli/RELEASING.md; do not invent an F1 report. - List every released
package@versioninCHANGELOG.md.
- Run
node scripts/release-packages.mjs validate <version>, then all checks required byapps/cli/RELEASING.md. Fix failures before continuing. - Commit, push, open the release PR, and merge it to
mainbefore dispatching the workflow. Never publish unmerged source or a non-main ref. - Dispatch
.github/workflows/release-cli.ymlfrommainin 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
--versioncommand. - Use the Linear integration to move every issue referenced by the version's
changelog section from
MergedUnreleasedtoReleasedMonitoring.
Safety
- Never add an npm token. Publishing must use GitHub Actions OIDC.
- Confirm every npm package trusts
cyrusagents/cyrusandrelease-cli.ymlbefore 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.
FAQ
What does the release skill do?
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.
How do I install release?
Run npx skills add https://github.com/cyrusagents/cyrus --skill release in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/release/ (personal) or .claude/skills/release/ (project).
Which AI agents can use release?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is release safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains release?
It is published by cyrusagents in cyrusagents/cyrus. It has 831 recorded installs.
More from cyrusagents/cyrus
cyrus-setup
cyrusagents/cyrus
Set up Cyrus end-to-end — install prerequisites, configure authentication, create integrations (Linear, GitHub, Slack), add repositories, and launch. Run this once to get Cyrus running as a background agent.
cyrus-setup-linear
cyrusagents/cyrus
Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.
cyrus-setup-claude-auth
cyrusagents/cyrus
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
cyrus-setup-github
cyrusagents/cyrus
Configure GitHub for Cyrus — gh CLI login and git config for PRs, with optional webhook setup to enable @mention responses in PR comments, automated rebases and merges, and auto-fixing based on CI failures (coming soon).
cyrus-setup-prerequisites
cyrusagents/cyrus
Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
cyrus-setup-endpoint
cyrusagents/cyrus
Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。