agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/release-standards/SKILL.md

release

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Guide the release process — semantic versioning, release modes, and the start/finish/promote/deploy sequence. Use when: cutting a release, deciding a semantic version bump, promoting a release candidate to stable, recording a deployment. Not for: writing the changelog entries themselves — use /changelog; the deployment mechanics — use /deploy. Keywords: release, semantic versioning, version bump, release candidate, promote, 發布, 語意化版本, 發版流程.

197 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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Update version files: - Update package.json and related version references

    line 80
  2. Distinctive:

    Run pre-release checks: - Verify tests, lint, standards compliance, and issue/PR triage gate

    line 82
  3. Distinctive:

    Commit and push: - Commit version bump and push tags

    line 84
  4. Distinctive:

    Before bumping, scan open issues/PRs and make a conscious decision per item — do not rely on memory:

    line 88
  5. Very specific:

    After /release completes, the AI assistant should suggest:

    line 126

“Common” is measured: kept by at least 6 in 10 of the 186 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 Assistant | 發布助手

Guide the release process following Semantic Versioning and changelog best practices.

引導遵循語義化版本和變更日誌最佳實踐的發布流程。

Subcommands | 子命令

SubcommandModeDescription說明
startAllStart a release branch/process開始發布流程
finishCI/CDFinalize release (tag, merge)完成發布（標籤、合併）
promoteManual/HybridPromote RC to StableRC → Stable 晉升
deployManual/HybridRecord deployment to environment記錄部署紀錄
manifestManual/HybridGenerate build-manifest.json產生打包資訊清單
verifyManual/HybridVerify manifest consistency驗證清單一致性
changelogAllGenerate or update CHANGELOG.md產生或更新變更日誌
checkAllRun pre-release verification執行發布前檢查

Release Modes | 發布模式

Configure via uds init or uds config --type release_mode:

ModeDescription說明
ci-cdAutomatic publishing via CI/CD pipeline (default)CI/CD 自動發布（預設）
manualManual packaging + RC workflow手動打包 + RC 工作流程
hybridCI builds artifact + manual deploymentCI 建置 + 手動部署

Version Types | 版本類型

TypePatternnpm Tag用途
StableX.Y.Z@latestProduction release正式版
BetaX.Y.Z-beta.N@betaPublic testing公開測試
AlphaX.Y.Z-alpha.N@alphaInternal testing內部測試
RCX.Y.Z-rc.N@rcRelease candidate候選版本

Workflow | 工作流程

  1. Determine version - Decide version type based on changes (MAJOR/MINOR/PATCH)
  2. Triage open issues/PRs - gh pr list + gh issue list; classify each bring-in vs defer (XSPEC-265) / 掃描 issue/PR、每項二分（帶上 vs backlog）
  3. Update version files - Update package.json and related version references
  4. Update CHANGELOG - Move [Unreleased] entries to new version section
  5. Run pre-release checks - Verify tests, lint, standards compliance, and issue/PR triage gate
  6. Create git tag - Tag with vX.Y.Z format
  7. Commit and push - Commit version bump and push tags

Pre-release Issue/PR Triage Gate | 發版前 issue/PR triage 閘門 (XSPEC-265)

Before bumping, scan open issues/PRs and make a conscious decision per item — do not rely on memory:

ClassAction
Bring-inpatch dependabot PR / release-blocking bug / fix relevant to this version's theme → merge before bump
Defermajor PR, audit/enhancement issue, needs separate evaluation → record in signoff "deferred" + release-notes Known Issues
  • Confirm cross-project/sub-project-triage.md snapshot is recent (≤7 days); refresh if stale.
  • Record the result in the release sign-off (Tier-1): Pre-release issue/PR triage | PASS | N PRs / M issues: X merged / Y deferred.
  • Do not require emptying the backlog — only that every item has a conscious decision + a record. 不要求清空 backlog，只要求每項有意識決策 + 留紀錄。

Version Increment Rules | 版本遞增規則

Change TypeIncrementExample
Breaking changesMAJOR1.9.5 → 2.0.0
New features (backward-compatible)MINOR2.3.5 → 2.4.0
Bug fixes (backward-compatible)PATCH3.1.2 → 3.1.3

Usage | 使用方式

CI/CD Mode (default)

  • /release start 1.2.0 - Start release process for v1.2.0
  • /release changelog 1.2.0 - Update CHANGELOG for v1.2.0
  • /release finish 1.2.0 - Finalize and tag v1.2.0
  • /release check - Run pre-release verification

Manual Mode (RC workflow)

  • /release start 1.2.0-rc.1 - Create RC version
  • uds release manifest - Generate build-manifest.json
  • uds release deploy staging - Record staging deployment
  • uds release deploy staging --result passed - Record test result
  • /release promote 1.2.0 - Promote RC to stable
  • uds release deploy production - Record production deployment
  • uds release verify - Verify manifest consistency

Next Steps Guidance | 下一步引導

After /release completes, the AI assistant should suggest:

發布流程完成。建議下一步 / Release process complete. Suggested next steps:

  • 驗證 npm 發布狀態 npm view <pkg> dist-tags ⭐ Recommended / 推薦 — Verify npm publication status
  • 建立 GitHub Release 並撰寫發布說明 — Create GitHub Release with notes
  • 通知利害關係人新版本已發布 — Notify stakeholders of new release

Reference | 參考

  • Changelog Format Guide — Read it when writing or reviewing a changelog entry.
  • Release Workflow Guide — Read it when actually cutting a release, step by step.
  • Semantic Versioning Guide — Read it when deciding whether a change is major, minor or patch.
  • Detailed guide: guide.md
  • Core standard: versioning.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/release

For complete AI agent behavior definition, see the corresponding command file: /release

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.

Check your setup, free