maigo

讀當前 branch 對應 PR 的 review 意見，列出讓使用者挑、提路由計畫確認後，逐項走 /maigo:quick · go · team 處理。讀不到 PR 直接擋下。

把記憶層裡反覆出現、convention 形狀的條目，畢業成常駐 skill——orchestrator 主持逐筆 propose / 使用者確認，確認的批次委派 🎀 愛音寫 skill（quick 模式），綠後退役來源記憶。

從當前 branch 的 commits / diff 產 GitHub PR title 與 description。Orchestrator 前置抓料，燈 (Tomori) 套 `github-title-description` skill 寫草稿。

診斷 Maigo 環境與專案配置。檢查 gh CLI、記憶層目錄、以及 Taki (Verifier) 是否能跑。

MyGO!!!!! 跑一遍——樂奈先看、燈寫計畫、愛音動手、爽世擋、立希驗。

按 Tomori 的計畫實作 code 變更。遵守既有慣例，不擴大 scope。

探索 codebase。在 Anon 動手之前，幫忙摸清楚相關檔案、慣例與影響面。**不寫 code**。

嚴格審查 Anon 的實作或外部 PR。預設 BLOCKED，要被 evidence 說服才放行。依 `skills/strict-review` 操作。

跑 test、lint、type check。給出真實的驗證結果——不靠 vibe，靠 exit code。

把混亂的需求與探索結果，結構化成可執行的步驟計畫。寫到 `.maigo/plan.md`。**不寫實作 code**。

This skill should be used when working in the apache/airflow repository as a contributor (not as a Dag author). It surfaces the conventions Airflow's own AGENTS.md enforces — naming, Breeze/uv environment, Ruff/Mypy style, coding rules, pytest patterns, PR hygiene — so any task (review, quick-fix, refactor) in airflow follows them.

This skill should be used when drafting a git commit message (new commit, `git commit --amend`, or a squash/rewrite message) from staged or proposed changes. It produces a user-impact subject and a concise body listing changed behaviour and breaking-change / newsfragment / related-PR pointers, deliberately avoiding motivation paragraphs (which belong in the PR description, not the commit log).

This skill should be used when working in the `commitizen-tools/commitizen` repository as a contributor (not as a downstream `[tool.commitizen]` user). It surfaces the conventions from the repo's own AGENTS.md — uv + poe tasks, conventional commits enforced by commitizen itself, ruff/mypy linting, pytest, and PR guidelines — so any task (review, quick-fix, refactor) in commitizen follows them.

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.

This skill should be used when writing or reviewing cross-file links inside Maigo source files (`agents/*.md`, `commands/*.md`, `skills/*/SKILL.md`). It enforces that cross-source links use absolute GitHub URLs — relative links break `mkdocs build --strict` because these files are dual-context (raw GitHub view + include-markdown shim into `docs/`).

3 hooks across 3 events