MiniMax shares its coding team’s agent workflows

MiniMax’s public repository contains methods its team says it uses to build MiniMax Code. A skill is a folder containing instructions in a SKILL.md file. Developers can take one skill separately: the README describes copying its folder into ~/.agents/skills, then opening a new MiniMax Code session and listing the available skills with /skills.

Give reviewers a separate starting point

The review procedure gives a fresh reviewing agent only the code changes, the requirement and actual test commands and output, including failed and skipped tests. It excludes the author’s conversation, plan and self-assessment. Without a requirement, it says to stop and ask. Reviewers check whether tests exercise the requirement, rather than merely pass. The author then opens the cited code and confirms each problem before fixing it and rerunning relevant tests; rejected findings need recorded reasons.

Ask what happens to long commands

The command checklist asks whether moving work into the background preserves the process or restarts it, and whether deadlines reset. It also asks how results arrive, where large output goes, and who cleans up tasks when the user stops or the process exits. Another question concerns unread results after the conversation is shortened to save space. These are inspection questions, not assurances that a particular agent implements those behaviors.

MarkTechPost provides secondary coverage of the release.