The first stack in MCode Stack: the workflows and self-check skills of
Ronny, R&D lead of MiniMax Code. Most skills pair with an article in the
MCode Engineering Notes series (see ../../notes/).
In Claude Code, one command installs this stack. In a shell:
claude plugin install ronny --marketplace MiniMax-AI/mcode-stackInside a session:
/plugin install ronny --marketplace MiniMax-AI/mcode-stackOlder Claude Code can add the marketplace first, then install:
/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stackIn Codex, add the marketplace, then install from the Plugins Directory or the CLI:
codex plugin marketplace add MiniMax-AI/mcode-stack
codex plugin add ronny@mcode-stackIn MiniMax Code, copy this whole directory into the local plugin directory
shown by mcode plugin marketplace list, or copy single skills into
~/.agents/skills/. See the repository README.
| Skill | What it does | Notes |
|---|---|---|
independent-review |
Review a diff from a clean context: only diff, requirement and test results; structured findings verified before fixing | 01 |
subagent-split-check |
Decide whether work goes to a subagent or stays in the main loop; merge existing subagents back step by step | 01 |
harness-experiment |
Run a harness change as an experiment: small eval, one change, repeated runs, flipped tasks | 01, 02, 05 |
tool-budget-audit |
Measure what tools cost in context and pick between trimming, tool search and programmatic tool calling | 02 |
long-session-check |
Drop, summarize or write to file; when to compact vs. start fresh; review compaction and memory design | 03 |
handoff-doc |
Write a hand-off doc (goal, decisions, ruled out, next step) so a new session can pick up | 01, 03 |
long-command-check |
Ten-point audit of how an agent runs long shell commands and background tasks | 04 |
context-tax-audit |
Inventory what is injected into every request and how it affects the prompt cache | 05 |
trajectory-review |
Review how the agent got its result, not only whether it passed | - |
Everyday engineering skills, also published in
agentara/skills
and adapted from Google Engineering Practices (CC-BY 3.0). See
NOTICE.md for licenses.
| Skill | What it does |
|---|---|
engineering-code-review |
Review a change for code health: design, functionality, complexity, tests, approval risk |
engineering-review-comments |
Write clear, severity-labeled review comments that explain the reasoning |
engineering-review-feedback |
Handle reviewer comments as the author: fix, clarify, resolve disagreements |
engineering-small-prs |
Split large features, refactors and migrations into small reviewable PRs |
engineering-change-descriptions |
Write PR and commit descriptions that say what changed and why |
engineering-emergency-changes |
Decide whether a hotfix is a real emergency and run expedited review safely |
Plain-text versions of the checklists live in checklists/.