maigo
01Plugin Claude Code
MyGO!!!!! agent orchestration for Claude Code.
Plugin Claude Code
MyGO!!!!! agent orchestration for Claude Code.
Plugin Claude Code
A general-purpose development workflow for an agent, described as being driven by MyGO!!!!! and built around multiple agents and reviews.
Instructions file CodexOpenCode
Instructions for Lee-W/maigo, covering maigo contributor instructions for codex agents, tone, agent & narrator emoji — quick-ref (always in context), hooks vs skills boundary and verification quirks.
Instructions file
Instructions for Lee-W/maigo, covering maigo contributor instructions for claude code agents, tone, agent & narrator emoji — quick-ref (always in context), hooks vs skills boundary and verification quirks.
Agent
An implementation agent in the MyGO!!!!! workflow that turns an approved coding plan into repository changes. It follows existing project conventions and reports when the plan is incomplete or unclear.
Agent
A codebase-exploration agent examines relevant files, patterns, conventions, and possible side effects before implementation. It reports findings without writing code.
Agent
A strict code-review agent that checks implementations and pull requests against evidence and a fixed checklist. It can apply different review tones and levels of detail depending on whether the change is internal or external.
Agent
A verification agent from the MyGO!!!!! group that runs a project’s tests, lint checks, and type checks. It reports the actual commands, exit codes, and important output without changing the code.
Agent
A planning agent that turns unclear requirements and exploration results into an actionable sequence of steps. It records implementation plans, review checklists, issue-triage rubrics, or draft pull-request descriptions, depending on how it is called.
Command
A command that reads review comments on the pull request linked to your current Git branch and helps route each comment to a suitable workflow. A pull request is a proposed code change awaiting review on GitHub.
Command
A command that maintains a work board in .maigo/board.md for issues, your pull requests, and pull requests you are reviewing. A pull request is a proposed code change awaiting review or merging.
Command
A command that turns repeated, structured rules or workflows stored in the agent’s memory into permanent skills. It reviews possible candidates with the user, then prepares the approved skills and checks them.
Command
從當前 branch 的 commits / diff 產 GitHub PR title 與 description。Orchestrator 前置抓料,燈 (Tomori) 套 github-title-description skill 寫草稿。.
Command
A read-only diagnostic command for checking whether the Maigo workflow and project are configured correctly. It checks command-line tools, memory files, test settings, retry logs, and recent token-use records.
Command
Command "go" from Lee-W/maigo, covering /maigo:go, 使用, 流程 and 失敗處理.
Command
A read-only command that lists shared memory entries stored across projects, with an optional filter by memory type.
Command
A command for small, focused code changes, such as correcting documentation or adding a type hint, with a lightweight review and test check.
Command
A command that saves a user's preference, habit, feedback, or reference in shared memory stored across projects.
Command
Command "repo-audit" from Lee-W/maigo, covering /maigo:repo-audit, 使用, 四個資料源(全 read-only), a. 已合併可刪的 branch and b. 未關 pr(需要 gh cli).
Command
A command that finds preferences, agreements, and lessons from a conversation and asks whether each should be saved in shared memory or project documentation. It can reuse the project's existing remembering process.
Command
A strict review workflow for checking an existing GitHub pull request, branch, or range of commits without implementing changes.
Command
A workflow that turns a ready GitHub issue into an implementation task, from gathering its details through planning, coding, review, and verification.
Command
跟 /maigo:go 一樣的流程,但 Soyo + Taki 並行跑。Wall-clock 省 30%;fallback 用 --force-sequential。.
Command
A command for reviewing GitHub issues from a maintainer's perspective, meaning deciding how each incoming report should be handled.