ronny — Claude Code plugin: workflows and installation
ronny is a Claude Code plugin with skills for code review, agent workflows, and checking agent output. It comes into play for reviewing changes, delegating work, and auditing how agents operate.
MIT ★ 741 updated 2026-11-11
/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stackWhat ronny does
ronny groups skills for reviewing a diff from a clean context, checking whether work should go to a subagent, and examining how an agent reached its result. Other skills cover tool-related context costs, long sessions, and shell commands. The long-command audit has ten checks.
The collection also includes agent briefs, hand-off notes for new sessions, and ways to turn recurring corrections into tests, linters, hooks, or CI steps. Engineering skills cover splitting large changes into smaller PRs, writing change descriptions, and reviewing emergency fixes.
What it helps with
- review a diff from a clean context
- decide whether to delegate work to a subagent
- audit tool use and context costs
- split a large change into smaller PRs
- turn a recurring correction into a CI check
Example prompts for the agent
- Review this diff independently and verify each finding before proposing a fix.
- Decide which parts of this task should go to a subagent and which should stay in the main workflow.
- Split this migration into small PRs and write a description of the changes.
How to install ronny
Plugin marketplace
/plugin marketplace add MiniMax-AI/mcode-stack/plugin install ronny@mcode-stackStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about ronny
How do I install ronny in Claude Code?
In a Claude Code session, add the marketplace with /plugin marketplace add MiniMax-AI/mcode-stack, then install the plugin with /plugin install ronny@mcode-stack.
What does ronny do?
It provides skills for code review, subagent coordination, and checking AI agents’ work. The collection also covers small PRs, change descriptions, and emergency changes.
What do ronny’s audit skills check?
They cover tool costs in context, long-running shell commands, and the steps an agent took to reach its result.
Source text
ronny · MIT
# ronny 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/`](../../notes/)). ## Install In Claude Code, one command installs this stack. In a shell: ```bash claude plugin install ronny --marketplace MiniMax-AI/mcode-stack ``` Inside a session: ```bash /plugin install ronny --marketplace MiniMax-AI/mcode-stack ``` Older Claude Code can add the marketplace first, then install: ```bash /plugin marketplace add MiniMax-AI/mcode-stack /plugin install ronny@mcode-stack ``` In Codex, add the marketplace, then install from the Plugins Directory or the CLI: ```bash codex plugin marketplace add MiniMax-AI/mcode-stack codex plugin add ronny@mcode-stack ``` In 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](../../README.md#quick-start). ## Skills | Skill | What it does | Notes | | --- | --- | --- | | [`independent-review`](skills/independent-review/SKILL.md) | Review a diff from a clean context: only diff, requirement and test results; structured findings verified before fixing | 01 | | [`subagent-split-check`](skills/subagent-split-check/SKILL.md) | Decide whether work goes to a subagent or stays in the main loop; merge existing subagents back step by step | 01 | | [`harness-experiment`](skills/harness-experiment/SKILL.md) | Run a harness change as an experiment: small eval, one change, repeated runs, flipped tasks | 01, 02, 05 | | [`tool-budget-audit`](skills/tool-budget-audit/SKILL.md) | Measure what tools cost in context and pick between trimming, tool search and programmatic tool calling | 02 | | [`long-session-check`](skills/long-session-check/SKILL.md) | Drop, summarize or write to file; when to compact vs. start fresh; review compaction and memory design | 03 | | [`handoff-doc`](skills/handoff-doc/SKILL.md) | Write a hand-off doc (goal, decisions, ruled out, next step) so a new session can pick up | 01, 03 | | [`long-command-check`](skills/long-command-check/SKILL.md) | Ten-point audit of how an agent runs long shell commands and background tasks | 04 | | [`context-tax-audit`](skills/context-tax-audit/SKILL.md) | Inventory what is injected into every request and how it affects the prompt cache | 05 | | [`trajectory-review`](skills/trajectory-review/SKILL.md) | Review how the agent got its result, not only whether it passed | - | | [`agent-brief`](skills/agent-brief/SKILL.md) | Before delegating: stakes, our own hypothesis, scope in our words, what "verified" means, and the mode | - | | [`evidence-first-review`](skills/evidence-first-review/SKILL.md) | When an agent says done: evidence before summary, what each check misses, its silent decisions, try to break it | - | | [`review-capacity-check`](skills/review-capacity-check/SKILL.md) | Before launching more sessions: is finished work piling up faster than we can stand behind it | - | | [`taste-to-checks`](skills/taste-to-checks/SKILL.md) | Turn a correction we keep making into a test, lint, hook or CI step, proven on the old mistake | - | ### Engineering practice Everyday engineering skills, also published in [agentara/skills](https://github.com/agentara/skills/tree/main/skills/engineering) and adapted from Google Engineering Practices (CC-BY 3.0). See [`NOTICE.md`](NOTICE.md) for licenses. | Skill | What it does | | --- | --- | | [`engineering-code-review`](skills/engineering-code-review/SKILL.md) | Review a change for code health: design, functionality, complexity, tests, approval risk | | [`engineering-review-comments`](skills/engineering-review-comments/SKILL.md) | Write clear, severity-labeled review comments that explain the reasoning | | [`engineering-review-feedback`](skills/engineering-review-feedback/SKILL.md) | Handle reviewer comments as the author: fix, clarify, resolve disagreements | | [`engineering-small-prs`](skills/engineering-small-prs/SKILL.md) | Split large features, refactors and migrations into small reviewable PRs | | [`engineering-change-descriptions`](skills/engineering-change-descriptions/SKILL.md) | Write PR and commit descriptions that say what changed and why | | [`engineering-emergency-changes`](skills/engineering-emergency-changes/SKILL.md) | Decide whether a hotfix is a real emergency and run expedited review safely | Plain-text versions of the checklists live in [`checklists/`](checklists/).
© Ronny (MiniMax Code team) · MIT · MiniMax-AI/mcode-stack