Skip to content

MiniMax-AI/mcode-stack / stacks/ronny/skills/independent-review

independent-review

Verified

Review a code change from a clean context, the way an outside reviewer would. Use after the agent finishes an implementation, before merging, or when asked for an independent or second-opinion review of a diff.

Independent Review

The agent that wrote the code has made many small decisions and convinced itself of each one. A reviewer that inherits that conversation tends to follow the same reasoning and miss the same things. This skill keeps the reviewer outside the author's context.

Companion to MCode Engineering Notes 01, "More subagents isn't better".

1. Give the reviewer exactly three inputs

Collect these, and nothing else:

  1. The diff. For example git diff <base>...HEAD, or the staged changes.
  2. The requirement. The issue, spec, task description or acceptance criteria the change is supposed to satisfy.
  3. Test results. The commands that were run and their real output, including failures and skipped tests.

Do not pass the author's conversation, plan, intermediate reasoning or self-assessment. The question the reviewer answers is "does this change meet the requirement?", not "does the author's reasoning hold up?".

If the requirement is missing, stop and ask for it. A review without a requirement can only check style.

2. Run the review in a fresh context

Prefer one of these, in order:

  • A subagent or task started with only the three inputs above. This is a black-box check with a clean boundary and a compact result, which is the kind of split that is worth a subagent.
  • A built-in review command or skill, if your agent has one, started in a new session.
  • A new session in which you paste the three inputs.

Ask the reviewer to look in particular for:

  • Assumptions the code relies on but does not check (null or empty input, callers that "already validate", ordering, concurrency, error paths).
  • Requirement items that the diff does not cover.
  • Tests that pass without actually exercising the requirement. Tests written by the same agent share its blind spots, so check whether they cover the requirement, not only whether they pass.
  • Behaviour changes outside the stated scope.

3. Get findings back in a fixed structure

Each finding must have:

FieldContent
ProblemWhat is wrong, in one or two sentences
LocationFile and line or function
ReasonWhy it is wrong, tied to the requirement or to concrete code
Severityblocking / should-fix / nit

Findings without a location or a reason are treated as opinions, not defects.

4. Verify before fixing

Back in the main loop, do not apply findings wholesale. For each one:

  1. Open the real code at the stated location.
  2. Confirm the problem exists, ideally with a failing test or a concrete input.
  3. Only then fix it, and rerun the relevant tests.
  4. Record findings you rejected and why, so the next review does not raise them again.

Output

End with a short summary: findings confirmed and fixed, findings rejected (with the reason), and anything still open.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexVerifiedInstall