Menú
提交指引與提交前的必要品控閘門。將變更提交到 git repo 或推送到 remote 前，需完成所有品控項目。包括審查、文檔同步與 changelog 門檻。
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 | commit |
| description | 提交指引與提交前的必要品控閘門。將變更提交到 git repo 或推送到 remote 前，需完成所有品控項目。包括審查、文檔同步與 changelog 門檻。 |
在不破壞既有工作樹與提交邊界的前提下，安全地完成本地 commit 與可選 push。 確保所有審查、文件同步與 changelog 門檻均已確實完成。
檢查目前的 git 變更狀態。 識別變更範圍。 確認暫存變更中是否包含代碼變更。
若變更範圍涉及代碼變更，確認變更已通過必要的審查與驗證。 若在審查中發現問題，修復後暫存。
使用 docs-project、maintain-project-constraints 技能更新項目文檔。
遵循當中的指引，確保文檔與 repo 保持一致。
若存在代碼變更，使用 update-project-html 檢查並更新項目架構圖。
若存在代碼變更，先執行 apltk codegraph --help 與相關子命令 --help，再按 live CLI 指引同步代碼圖，確保代碼圖與實際代碼同步。
若 CLAUDE.md 或 AGENTS.md 缺少 apltk codegraph 的引用，必須添加。
依使用者的 staging 邊界建立 commit。
提交訊息須遵循 references/commit-messages.md。
只有在使用者明確要求更新 remote 時才 push。
references/commit-messages.md：提交訊息格式references/branch-naming.md：分支命名慣例