mcode-stack

The workflows and skills the MiniMax Code team uses to build MiniMax Code. Open source, install and use.

New — Created in the last 30 days
Active — Updated in the last 14 days

Works with

Claude

View on GitHub

462 GitHub stars (462)

+462 in 4 days

Stars gained per day · daily snapshots since Oct 29

Stars gained between daily snapshots
Period	New stars
Oct 30	+241
Oct 31	+13

17 skills (17 skills found in its SKILL.md files)
35 forks (35 forks)
2d ago last update (Last updated 2d ago)

Install

Skills CLI

npx skills add MiniMax-AI/mcode-stack

Asks which skills and agents to install. Just one: npx skills add MiniMax-AI/mcode-stack --skill lifting-loops — add -g for every project.

Claude Code

git clone https://github.com/MiniMax-AI/mcode-stackcp -r "mcode-stack/stacks/jiachen/skills/lifting-loops" ~/.claude/skills/

Copies the lifting-loops skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add MiniMax-AI/mcode-stack

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

Filter skills

In the author's own words, from each skill's SKILL.md.

lifting-loops

Finds loops where the user keeps acting as a manual step for agents (retrying, judging output, approving, carrying context, starting the same task by hand, doing the agent's work) and proposes how to lift the user out: delete a stale rule, change a skill / AGENTS.md / playbook, add a script or metric, add a skill or scheduled task, or advise the user. Keeps a private loop ledger and promotes Clau…
stacks/jiachen/skills/lifting-loops/SKILL.md on GitHub (opens in a new tab)
making-content

Content production in three modes: rewrite, Xiaohongshu (小红书) image post, short video. Rewrite (default): turns an AI-sounding Chinese or mixed Chinese-English draft (post, newsletter, engineering blog, commentary) into the author's restrained style: few emoji, short paragraphs, hedged claims, neutral wording, English terms split by spaces. Triggers: 按我的风格改, 去 AI 味, 润色, 改改这篇, or a vague 帮我改改 when…
stacks/jiachen/skills/making-content/SKILL.md on GitHub (opens in a new tab)
context-tax-audit

Inventory everything an agent injects into each request besides the user's message, such as system prompt, environment info, skill list, tool definitions, per-turn context blocks and reminders, and check necessity, frequency, precision, position and prompt-cache impact. Use when reviewing an agent's prompt assembly, chasing low cache hit rates, or trimming per-turn overhead.
stacks/ronny/skills/context-tax-audit/SKILL.md on GitHub (opens in a new tab)
engineering-change-descriptions

Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing ch…
stacks/ronny/skills/engineering-change-descriptions/SKILL.md on GitHub (opens in a new tab)
engineering-code-review

Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, a…
stacks/ronny/skills/engineering-code-review/SKILL.md on GitHub (opens in a new tab)
engineering-emergency-changes

Use when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline claims expedited review or relaxed process. TRIGGER on "emergency change", "hotfix", "prod incident", "major security hole", "must ship today", "hard deadline", "bypass review", or "fast-track this PR" for qualification only. DO NOT TRIGGER for ordinary urgency, soft deadlines, F…
stacks/ronny/skills/engineering-emergency-changes/SKILL.md on GitHub (opens in a new tab)
engineering-review-comments

Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descri…
stacks/ronny/skills/engineering-review-comments/SKILL.md on GitHub (opens in a new tab)
engineering-review-feedback

Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer com…
stacks/ronny/skills/engineering-review-feedback/SKILL.md on GitHub (opens in a new tab)
engineering-small-prs

Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how should I break this up?", or implementation scope too broad for one review. DO NOT TRIGGER for full code review, PR descri…
stacks/ronny/skills/engineering-small-prs/SKILL.md on GitHub (opens in a new tab)
handoff-doc

Write a hand-off document so a fresh session or another person can continue the current task without the chat history. Use when switching tasks, after several compactions, before clearing a session, or when asked to write a handoff, brief, or progress doc.
stacks/ronny/skills/handoff-doc/SKILL.md on GitHub (opens in a new tab)
harness-experiment

Run a harness change as a controlled experiment, with a small end-to-end eval, one change at a time, repeated runs, and looking at flipped tasks, request count, tokens and cache hits, not just the average score. Use before and after changing prompts, tools, skills, subagent layout, compaction or other agent scaffolding, or when asked whether a change helped.
stacks/ronny/skills/harness-experiment/SKILL.md on GitHub (opens in a new tab)
independent-review

Review a code change from a clean context, the way an outside reviewer would. Use after the agent finishes an implementation, before merging, or when asked for an independent or second-opinion review of a diff.
stacks/ronny/skills/independent-review/SKILL.md on GitHub (opens in a new tab)
long-command-check

Audit how an agent harness runs long shell commands, covering foreground wait limits, moving to background without re-running, timeouts, completion notification, polling, output size, cleanup and behaviour after compaction. Use when building or reviewing an agent's shell or background-task tool, or when an agent hangs on dev servers, long builds or test runs.
stacks/ronny/skills/long-command-check/SKILL.md on GitHub (opens in a new tab)
long-session-check

Check how an agent or a working session handles long conversations, covering tool-result clearing, compaction, what gets written to files, when to start a new session, and how memory is scoped. Use when a long session starts forgetting constraints, after several compactions, or when reviewing an agent's compaction and memory design.
stacks/ronny/skills/long-session-check/SKILL.md on GitHub (opens in a new tab)
subagent-split-check

Decide whether a piece of work should go to a subagent or stay in the main agent loop. Use before spawning subagents, when designing a multi-agent architecture, or when auditing an existing set of subagents for merging back.
stacks/ronny/skills/subagent-split-check/SKILL.md on GitHub (opens in a new tab)
tool-budget-audit

Audit how much context an agent's tools consume, through tool definitions and tool results, and decide whether to trim the catalog, add tool search, or add programmatic tool calling. Use when an agent has many tools or MCP servers, picks the wrong tools, or burns context on tool output.
stacks/ronny/skills/tool-budget-audit/SKILL.md on GitHub (opens in a new tab)
trajectory-review

Review how an agent reached its result, not only whether the result passed, covering tools called, detours, unverified assumptions and wasted round trips, and turn the findings into concrete harness or prompt fixes. Use after an agent task finishes or fails, when an eval task flips, or when asked to look at the process behind a result.
stacks/ronny/skills/trajectory-review/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.

Encoders & Decoders

Hash Generators

Code Formatters

HTML Tools

JavaScript Tools

Network Tools

Database Tools

Development Tools

Miscellaneous Tools

mcode-stack