minimax-ai/mcode-stack

review-capacity-check

Check whether finished agent work is piling up faster than we can stand behind it, and fix that by tightening automatic checks or running fewer parallel sessions instead of starting another one.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/minimax-ai/mcode-stack --skill review-capacity-check

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Review Capacity Check

Running five MiniMax Code sessions in parallel is easy. Standing behind five results is not. Every agent we launch costs review time later. When finished work waits longer than it took to produce, we are not reviewing any more, we are hoping.

1. Count the queue

Before starting another session, list what is already done but not yet accepted by us: open agent PRs, finished subagent outputs, analyses nobody has checked. For each, note the stakes (see agent-brief).

If more than a couple of high-stakes items are waiting, do not launch. Clear the queue or reduce what needs us.

2. Reduce what needs us, not the bar

In order of preference:

  1. Let checks do more: add a test, lint or CI step so a class of review is

automatic (see taste-to-checks).

  1. Make agents prove more: require the evidence block from agent-brief in

every result, so review starts from commands and output.

  1. Run fewer at once: fewer sessions we can defend beat more we cannot.

Skimming high-stakes work faster is not on the list.

3. Check the chain

In a pipeline (research agent, then writer, then reviewer), each later agent should read the original source, not only the previous agent's summary. Summaries drop caveats; three hops later the caveat is gone and the claim is stronger than the data. Check that the last agent's context includes the source files, logs or links, not just the hand-off text.

4. Weekly: what are we no longer practicing?

Write down one or two things the agent now always does for us (reading a stack trace, writing a migration, sizing a query). For each, decide on purpose: fine to let go, or keep doing it by hand now and then so we can still judge the agent's version.

Output

The queue with stakes, a decision (launch, clear first, or add a check), and the weekly list if it is that day.

References

dallo stesso repository

Altri Skills

Tutti gli Skills
minimax-ai
Community

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.

Installazioni / 1h
1
GitHub Stars
685
Aggiornato
10 nov
minimax-ai
Community

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. Use when a MiniMax Code session, subagent or cloud agent reports a task done, before merging its PR or acting on its analysis.

Installazioni / 1h
1
GitHub Stars
685
Aggiornato
10 nov
minimax-ai
Community

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.

Installazioni / 1h
1
GitHub Stars
685
Aggiornato
10 nov
minimax-ai
Community

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.

Installazioni / 1h
1
GitHub Stars
685
Aggiornato
10 nov