- name
SKILL.md
Beceri dosyası yayıncının deposunda kalır.
Kopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a cursor -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a claude-code -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a codex -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill evidence-first-review -a grok -yKopyalanan mesajı bir Grok Bot sohbetinde gönderin. Bot bu SKILL.md dosyasını GitHub'dan alır ve tüm Bot'larınızın paylaştığı becerilere ekler.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/evidence-first-reviewYayıncıdan
"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.mdGenel bakış
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.
SSS
stacks/ronny/skills/evidence-first-review/SKILL.md dosyasını yayıncıdan indirin veya yolu kopyalayıp depoyu açın. PlugMCP beceriyi listeler, dosyayı barındırmaz.
Yayıncı bunu şurada tutuyor: https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex ve Grok Build, yayıncının deposundan eklediğiniz bir SKILL.md dosyasını okuyabilir. Grok Bot, becerinin GitHub klasör bağlantısını bir sohbette gönderdiğinizde onu kurar.