Menu
協助完成自動化版本發佈。同步文檔、更新版本號、推送 tag 並建立 GitHub Release。
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Reads SPEC.md, validates technical feasibility through web research, finds quality reference implementations, confirms tech stack compatibility, then produces DESIGN.md (architecture design, external dependencies), CHECKLIST.md (verification strategy), Architecture Diff, and design-time refactoring plan. Not for use without a SPEC.md.
Helps users clarify vague requirements through structured conversation, producing a high-level design (PROPOSAL.md) with requirement summaries. Does not read any repo files — relies entirely on conversation. Suitable for requirement discussions, feature ideation, or greenfield project planning.
Executes FIX.md (from the qa skill) as the fix coordinator. The coordinator reads the fix plan, dispatches fix workers and regression test workers, verifies batch gates, and manages the execution flow — it does not write or fix code itself.
Executes PROMPT.md (from the plan skill) as the implementation coordinator. The coordinator reads the plan, dispatches workers, verifies batch gates, and manages the execution flow — it does not write implementation code itself.
Converts SPEC.md + DESIGN.md + CHECKLIST.md into a self-contained coordinator prompt (PROMPT.md) with complete task decomposition, dependency analysis, batch scheduling, and pre-written worker prompts. The generated PROMPT.md is consumed directly by the implement skill.
Reads spec documents and the review output REPORT.md, then generates a self-contained fix coordinator prompt (FIX.md) with issue inventory, dependency analysis, batch scheduling, regression test design, and pre-written worker prompts. The generated FIX.md is consumed directly by the fix skill.
| name | version-release |
| description | 協助完成自動化版本發佈。同步文檔、更新版本號、推送 tag 並建立 GitHub Release。 |
協助用戶完成自動化版本發佈流程。
CHANGELOG.md, docs/ 下所有項目文檔已經被同步到最新狀態檢查當前 git 分支是否為 default 分支（main 或 master）：
commit 技能提交所有待處理變更。推送到 remote。git merge --ff-only origin/<default>）。若有代碼變更，先執行 apltk codegraph --help 與相關子命令 --help，再按 live CLI 指引同步代碼圖，確保代碼圖與實際代碼同步。
若 CLAUDE.md 或 AGENTS.md 缺少 apltk codegraph 的引用，必須添加。
通過並行調度 subagents 完成變更的逐行深度閱讀，檢查文檔是否存在錯誤或遺漏。
若有，使用 docs-project、maintain-project-constraints 將文檔同步到最新。
確認所有文檔已更新。
更新 repo 的版本文件（如 pyproject.toml）。
使用 commit 技能提交並推送所有變更。
最後推送 version tag 並建立 GitHub release。
references/semantic-versioning.md：版本號選擇規則references/commit-messages.md：release commit 訊息格式references/branch-naming.md：分支命名慣例references/changelog-writing.md：CHANGELOG.md 與 Unreleased 維護規則references/readme-writing.md：README 只在必要時同步更新