- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/evidence-first-reviewDe l'éditeur
"All tests pass, ready to merge" is a claim, not evidence. We read what the agent actually ran before we read what it says about it. The bar for accepting the work: we could defend it to the person who will maintain it, and we can say what our checks would miss.
This skill is about owning the result. For a clean-context code review of the
diff itself, pair it with independent-review.
Open the transcript or tool log, not the final message. For each command that supports "done": did it run on the final code, did it exit 0, does the output say what the summary says? Typical gaps we find:
-t compaction that skipped the suite that matters;If we cannot fill the right column, we do not understand the check yet.
Ask the agent: which defaults did you pick, what did you leave out of scope, and where did you reinterpret the requirement because two parts clashed? These are the choices that end up in production without anyone deciding them. Each one is accepted, changed or sent back.
Ask: what would have to be true for this to be wrong? Then check that one thing ourselves. For analysis and docs, open two of the cited sources and recompute one number the conclusion depends on.
When we report the work to others, we lead with the evidence (commands and results), then: what was checked, one thing that was not, and the key decisions.
Review an agent's finished work by reading the evidence before its summary, naming what each check proves and what it misses, pulling out the decisions it made silently, and trying to falsify the resu
---name: evidence-first-reviewdescription: Review an agent's finished work by reading the evidence before its summary, naming what each check proves and…---# stacks/ronny/skills/evidence-first-review/SKILL.mdVue d'ensemble
Review an agent's finished work by reading the evidence before its summary, naming what each check proves and what it misses, pulling out the decisions it made silently, and trying to falsify the result before accepting it. Use when a MiniMax Code session, subagent or cloud agent reports a task done, before merging its PR or acting on its analysis.
FAQ
Téléchargez stacks/ronny/skills/evidence-first-review/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.