agentleFS
fitlab-aifitlab-ai/agent-infra/.agents/skills/release/SKILL.md

release

Skill88 starsChanged 20 days agoMITView on GitHub

执行版本发布流程。 当准备切出并发布新版本时使用。参数:版本号(X.Y.Z)。

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

Files
SKILL.md

版本发布

在单次调用中准备发布、展示最新事实快照并请求一次远端发布授权。状态由外部事实重建;具体以 Git、代码托管平台与包发布渠道为准,不维护第二套 journal。

1. 验证输入与人工检查点

验证唯一参数 {version} 是规范 SemVer,并确认 entropy 人工检查点已满足。为此读取最新 entropy 报告;报告存在未处置高风险项时停止,不得替用户批准发布。

2. 准备并检查发布事实

agent-infra-internal release-workflow inspect {version}

必须保留并展示该命令的完整非空 stdout。blocked 表示外部事实不可确认,不得当作 missing。未 prepared 时执行 prepare 并重新 inspect;已准备或部分发布时复用当前事实。unknown 必须 blocked。

agent-infra-internal release-workflow prepare {version} --entropy-report {path}

必须展示 prepare 的 status、error 和 operations,其中包括关闭当前版本里程碑及创建后续规划里程碑的结果。failed 或 blocked 时停止,不得请求发布授权;只有 prepare 成功且重新 inspect 得到的最新快照才可进入下一步。

prepare 后必须重新 inspect;不得重复已满足动作。

3. 展示快照并确认

展示最新 snapshot 的完整 JSON,包括 facts 中的所有渠道状态。只有当前会话中针对该快照的无歧义明确肯定答复才授权发布;否定、调整、疑问、歧义或中断均停止,不得 publish。快照变化后重新展示并重新确认。

4. 发布并复核

agent-infra-internal release-workflow publish {version}

逐 ref 普通 push;部分成功可重放,禁止 force push。core 保留已成功事实并返回 degraded,重跑只补未满足事实。操作后重新 inspect;unknown 必须 blocked。发布后的 inspect 必须展示完整快照;如果平台 Release、npm、Homebrew 或 smoke 仍为 pending,明确标出未完成项,不得把 Git ref 推送成功表述为完整发布。

5. 输出事实摘要

完整发布后渲染携带版本的下一步,不显示内部 action,也不直接跳到 post-release:

agent-infra-internal agent-client next-steps \
  --skill create-release-note \
  --version {version}

输出完整快照和 helper 的非空 stdout。

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.