菜单
This skill should be used whenever a maigo command produces a deliverable destined to be pasted elsewhere (a PR/issue comment, a reply draft, a commit message, a gh command draft). It mandates wrapping that content in a single fenced code block so the user gets raw, one-click-copyable markdown instead of a rendered-only version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
This skill should be used when assembling git commits — deciding what to stage, how to scope a bash/agent command's working directory, whether to amend an unreleased commit or stack a new one, and how to size a diff against the correct baseline. Applies to the commit-assembly step of /maigo:go, /maigo:quick, /maigo:team, and /maigo:address-comments, and to the orchestrator generally.
This skill should be used when the maigo orchestrator, running in the Claude Code harness, decides whether to delegate work to a subagent instead of doing it on the main thread, needs to keep a long task's acceptance criteria from drifting after context compaction, or needs to keep verification independent from whoever produced the work. Scope note: 只在 Claude Code harness 下才適用——這裡的 orchestrator context 會被計費、可能被壓縮、且可 spawn subagent 分攤負載；沒有 subagent 能力的 harness 不適用此 skill。
This skill should be used by all maigo agents at startup, before beginning work, to load relevant cross-project memory entries with relevance-based ordering and a 10-entry cap. Consumers: Raana, Tomori, Soyo, the orchestrator itself, and any future agent that reads ~/.config/maigo/memory/.
This skill should be used by the maigo orchestrator on every /maigo command, alongside narration, to govern the conversational conduct of the main dialogue — AskUserQuestion widget discipline and Taiwanese Mandarin word-choice norms.
This skill should be used when performing code review on a diff (whether implemented by another agent or an external PR), enforcing a strict reviewer stance, applying a mandatory 9-item checklist, demanding evidence, and giving specific改法 instead of vague critique.
This skill should be used when orchestrating the full MyGO!!!!! teammate flow — Raana explores, Tomori plans, Anon implements, Soyo reviews, Taki validates. Applies to /maigo:go and /maigo:team (both sequential and parallel variants).
| name | copyable-deliverable |
| description | This skill should be used whenever a maigo command produces a deliverable destined to be pasted elsewhere (a PR/issue comment, a reply draft, a commit message, a gh command draft). It mandates wrapping that content in a single fenced code block so the user gets raw, one-click-copyable markdown instead of a rendered-only version. |
Owner Agent: orchestrator（呈現 deliverable 給使用者時）
Consumers:
/maigo:review、
/maigo:triage-issue、
/maigo:describe-pr、
skills/github-title-description、
skills/commit-message
Deliverable = 使用者會拿去貼到別處的內容：PR comment / issue reply 草稿、
commit message 草稿、gh 指令草稿、PR title / description。
不適用：純對話 / 分析 / 背景說明、review verdict 的 judgement 段落 （checklist / evidence）、純狀態 / queue 表——除非使用者明確要求弄成可複製。
Deliverable 一律放進單一 fenced code block，內含 raw markdown。
````）——deliverable 內部若有三-backtick
code block（例：Test Plan 的指令）才不會把外層截斷。範例：
可整段複製貼到 GitHub PR comment：
````markdown
幾個問題想確認：
1. `auth.py:42` 的 early return 在 `token == None` 時會跳過 audit log，是預期行為嗎？
整體設計方向 OK，等回覆再 approve。
````
平台 render markdown 後，使用者從 UI 框選複製到的是 rendered 結果，不是 raw 語法—— 手動框選費工又容易在內部 code block 處截斷。一個 fenced block = 一鍵複製 = 零選取誤差。
Deliverable 內的 prose 段落一行連續到底，不手動斷行——表格列、list item、 fenced code block 內容不受影響（本來就一行一項 / 逐字保留）。
理由同上：hard-wrap 的段落，使用者每次改字都要重排、diff 也雜；一段一行才好 複製、好編輯、diff 乾淨。
commit-message 的 output 若直接 pipe 進 git commit -F -，不加外層 fence
（fence 會破壞 pipe）；呈現給使用者過目時才適用本 skill。這個 pipe vs 呈現的區分已在
commit-message 內部說明。