release
Skill3 starsChanged 9 months agoApache-2.0View on GitHub
Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
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.
MicrosoftSkillcreate-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
GrinvSkillchangelog-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
Microsoft AzureSkillcomponent-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
GrinvSkilldocs-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 AzureSkilldocumentation-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
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- bug-fixSkill
- changelog-updaterSkill
- code-auditSkill
- code-refactorSkill
- code-reviewerSkill
- code-review-workflowSkill
- ddd-architectSkill
- feature-developmentSkill
- git-doc-updaterSkill
- git-precommitSkill
- memory-checkpointSkill
- memory-updaterSkill
- project-initSkill
- readme-i18nSkill
- readme-updaterSkill
- roadmap-updaterSkill
- security-reviewerSkill
- skill-generatorSkill
- skill-health-checkSkill
- test-generatorSkill
The file
Files
版本發布工作流
描述
完整的版本發布準備流程,包含版本號更新、CHANGELOG 生成、文檔同步和部署檢查。
觸發條件
- 「準備發布」「release」「發布版本」
- 「REL: v1.2.0」
📦 發布流程
┌─────────────────────────────────────────────────────────────┐
│ Release Workflow │
├─────────────────────────────────────────────────────────────┤
│ Phase 1: 🔍 發布檢查 (Pre-release Check) │
│ ├─ 確認所有測試通過 │
│ ├─ 執行安全掃描 │
│ ├─ 檢查待處理問題 │
│ └─ 確認 main/master 分支狀態 │
├─────────────────────────────────────────────────────────────┤
│ Phase 2: 🔢 版本決定 (Version Decision) │
│ ├─ 分析變更類型 (MAJOR/MINOR/PATCH) │
│ ├─ 確認版本號 │
│ └─ 更新版本檔案 │
├─────────────────────────────────────────────────────────────┤
│ Phase 3: 📝 文檔更新 (Documentation) │
│ ├─ [changelog-updater] 更新 CHANGELOG │
│ ├─ [readme-updater] 更新 README │
│ ├─ [roadmap-updater] 標記完成項目 │
│ └─ 更新 API 文檔(如有) │
├─────────────────────────────────────────────────────────────┤
│ Phase 4: 🏷️ 標籤準備 (Tagging) │
│ ├─ 建立 Git tag │
│ ├─ 準備 release notes │
│ └─ 確認變更摘要 │
├─────────────────────────────────────────────────────────────┤
│ Phase 5: 🚀 發布 (Publish) │
│ ├─ 推送 tag │
│ ├─ 建立 GitHub Release │
│ └─ 觸發 CI/CD pipeline │
├─────────────────────────────────────────────────────────────┤
│ Phase 6: 📢 發布後 (Post-release) │
│ ├─ 更新 Memory Bank │
│ ├─ 通知相關人員 │
│ └─ 準備下一版本 │
└─────────────────────────────────────────────────────────────┘🔢 版本號規則 (SemVer)
MAJOR.MINOR.PATCH
MAJOR: 不相容的 API 變更 (Breaking Changes)
MINOR: 向下相容的新功能 (New Features)
PATCH: 向下相容的 Bug 修復 (Bug Fixes)版本號決定指南
| 變更類型 | 版本 | 範例 |
| Breaking API 變更 | MAJOR | 1.0.0 → 2.0.0 |
| 新功能(不破壞現有) | MINOR | 1.0.0 → 1.1.0 |
| Bug 修復 | PATCH | 1.0.0 → 1.0.1 |
| 安全修復 | PATCH | 1.0.0 → 1.0.1 |
| 文檔更新 | PATCH | 1.0.0 → 1.0.1 |
| 效能改善 | MINOR/PATCH | 視影響範圍 |
🚀 使用範例
基本用法
「準備發布」
AI 執行:
1. 🔍 執行發布前檢查
2. 🔢 分析變更,建議版本號
3. 📝 更新 CHANGELOG、README、ROADMAP
4. 🏷️ 準備 Git tag
5. 📊 生成發布清單指定版本
「REL: v2.0.0」
AI 執行:
1. 確認這是 MAJOR 版本(Breaking Changes)
2. 要求確認 breaking changes 清單
3. 執行完整發布流程📊 輸出格式
## 📦 發布準備報告
### 版本資訊
- **當前版本**: 1.1.0
- **建議版本**: 1.2.0 (MINOR)
- **原因**: 新增 3 個功能,無 breaking changes
### 🔍 發布檢查
| 檢查項目 | 狀態 |
|----------|------|
| 測試通過 | ✅ 42/42 |
| 安全掃描 | ✅ 無風險 |
| Lint | ✅ 0 errors |
| 文檔同步 | ✅ 已更新 |
### 📝 變更摘要
#### Added
- 用戶認證模組
- API 限流功能
- 匯出功能
#### Fixed
- 登入超時問題
- 資料同步錯誤
#### Changed
- 改進錯誤訊息
### 📁 更新的文件
- ✅ CHANGELOG.md - 新增 v1.2.0 區塊
- ✅ README.md - 更新功能列表
- ✅ ROADMAP.md - 標記 3 個完成項目
- ✅ pyproject.toml - 版本號更新
### 🏷️ Git 指令
```bash
git add -A
git commit -m "chore: release v1.2.0"
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags📋 Release Notes
## v1.2.0 (2026-01-15)
### ✨ New Features
- 用戶認證模組
- API 限流功能
- 匯出功能
### 🐛 Bug Fixes
- 修復登入超時問題
- 修復資料同步錯誤
### 📖 Documentation
- 更新 API 文檔
- 新增使用範例下一步
- 確認變更摘要無誤
- 執行上述 Git 指令
- 在 GitHub 建立 Release
---
## ⚙️ 配置選項
| 參數 | 說明 | 預設值 |
|------|------|--------|
| `--dry-run` | 只預覽不執行 | false |
| `--skip-tests` | 跳過測試 | false |
| `--prerelease` | 預發布 (alpha/beta/rc) | false |
| `--force` | 強制指定版本 | false |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
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.

