菜单
適用於使用者輸入 "wrap up", "close session", "完成任務" 或 "收尾" 時觸發。將自動執行包含程式碼提交、記憶鞏固（寫入 lessons.md）與知識萃取的標準收尾流程。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | wrap-up |
| description | 適用於使用者輸入 "wrap up", "close session", "完成任務" 或 "收尾" 時觸發。將自動執行包含程式碼提交、記憶鞏固（寫入 lessons.md）與知識萃取的標準收尾流程。 |
You must execute the following four phases sequentially. Do not ask for permission between phases; auto-apply the logic and present a consolidated final report in Traditional Chinese (zh-TW).
git status)。若有未提交的變更，請自動生成符合常規的 commit message 並提交 (Commit)。如有遠端分支，嘗試 Push。docs/ 或 .gemini/）。若有錯置，自動移動它們。.gemini/tasks/todo.md。將已完成的任務標記為完成 (Done)，並列出尚未完成的遺留任務 (Pending)。Review the entire session to extract knowledge. Categorize findings into the following specific locations:
GEMINI.md): 適用於整個專案的永久性架構決策或重要規範。.gemini/rules/): 針對特定目錄或技術棧的局部規則（例如：database-rules.md）。.gemini/tasks/lessons.md): 本次會話中 Gemini 犯的錯誤、掙扎的邏輯，或使用者糾正的痛點。必須提煉成「未來不再犯」的通用規則。.gemini/local.md): 僅限本機開發用的環境變數說明、暫存測試網址或個人筆記（不需要 Commit 的資訊）。Do not just suggest changes; physically write/update the files identified in Phase 2.
Analyze the conversation for self-improvement. Categories include:
Action Required:
Update GEMINI.md, create specific .gemini/rules/ files, or append rules to .gemini/tasks/lessons.md.
Format your response summary exactly like this:
[已應用的自我修正]
[無需動作]
Review the completed work for publishable value. Look for:
If publishable material exists:
Draft a short technical article or social media post in Traditional Chinese. Save it to docs/drafts/Title-of-Post.md.
Mention in your final output: "已在 docs/drafts/ 生成一篇技術分享草稿：[標題]"。
If no publishable material exists: Simply state: "本次會話無產出需額外發佈的內容。"
FINAL MANDATE: All interactions and the final consolidated report MUST be output in Traditional Chinese (zh-TW).