minimax-ai/mcode-stack

evidence-first-review

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.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/minimax-ai/mcode-stack --skill evidence-first-review

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Evidence-First Review

"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.

1. Evidence before summary

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:

  • tests run before the last edit;
  • a filter like -t compaction that skipped the suite that matters;
  • "fixed" with no reproduction before the fix;
  • a build that passed only because a step was skipped.

2. For each green check, one property it proves and one it does not

CheckProvesDoes not prove
New unit test passesthe function returns X for this inputthe caller passes that input; the test was written with the same wrong assumption
pnpm typechecktypes line upruntime behaviour
E2E with a mock modelthe loop wires upanything about real model output

If we cannot fill the right column, we do not understand the check yet.

3. Ask for the decisions list

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.

4. Try to break it

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.

5. Make sure we understand it

  • Pick a few lines of the diff at random and explain them without help.
  • For a large change, ask the agent for a short report that ends in three

questions about the change; we answer them before merging.

  • For a contested call, have a fresh subagent argue the other side, then

decide ourselves.

  • Last question to a fresh context: "What did I miss?"

6. Decide

  • Accept: the evidence matches, decisions are reviewed, we can name the gap.
  • Ask for more: missing evidence or an unexplained decision.
  • Get a human review: high stakes and we cannot say what the checks miss.

Output

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.

References

du même dépôt

Autres Skills

Tous les Skills
minimax-ai
Communauté

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, author review-feedback responses, or non-code safety questions unless code review is requested.

Installations / 1h
1
GitHub Stars
685
Mis à jour
10 nov.
minimax-ai
Communauté

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.

Installations / 1h
1
GitHub Stars
685
Mis à jour
10 nov.
minimax-ai
Communauté

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.

Installations / 1h
1
GitHub Stars
685
Mis à jour
10 nov.
minimax-ai
Communauté

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 Claude Code auto-memory into artifacts. With a task already in the session, reflects on that session; in

Installations / 1h
1
GitHub Stars
685
Mis à jour
10 nov.