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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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:
…
The line at the top of this page pins the label git:20261028.c889a19, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_q6khg2d5smwzbp3k
GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/independent-review
GET https://markdownregistry.com/api/v1/blob/6f2b1a1cf6f05bf482df54f439925e35f19b40e73ee1bed3451547f271bbe457
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
minimax-ai/mcode-stack · stacks/jiachen/skills/lifting-loops/SKILL.md · Finds loops where the user keeps acting as a manual step for agents (retrying, judging output, approving, carrying…
minimax-ai/mcode-stack · stacks/jiachen/skills/making-content/SKILL.md · Content production in three modes: rewrite, Xiaohongshu (小红书) image post, short video. Rewrite (default): turns an…
minimax-ai/mcode-stack · stacks/ronny/skills/context-tax-audit/SKILL.md · Inventory everything an agent injects into each request besides the user's message, such as system prompt, environment…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-change-descriptions/SKILL.md · Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-code-review/SKILL.md · Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-emergency-changes/SKILL.md · Use when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-review-comments/SKILL.md · Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-review-feedback/SKILL.md · Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving…
minimax-ai/mcode-stack · stacks/ronny/skills/engineering-small-prs/SKILL.md · Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into…
minimax-ai/mcode-stack · stacks/ronny/skills/handoff-doc/SKILL.md · Write a hand-off document so a fresh session or another person can continue the current task without the chat history…
minimax-ai/mcode-stack · stacks/ronny/skills/harness-experiment/SKILL.md · Run a harness change as a controlled experiment, with a small end-to-end eval, one change at a time, repeated runs, and…
benchflow-ai/benchflow · benchmarks/followup-bench/SKILL.md · Incorporate feedback from an independent code reviewer to improve your solution. The reviewer is a different agent that…
lawzava/megapowers · plugins/megapowers/skills/independent-review/SKILL.md · Use when security, auth, billing, concurrency, data integrity, or another high-stakes artifact needs adversarial review…
ramboz/jig · hosts/copilot/.github/skills/independent-review/SKILL.md · Build the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without…
ramboz/jig · hosts/claude/skills/independent-review/SKILL.md · Build the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without…
ramboz/jig · hosts/codex/plugins/jig/skills/independent-review/SKILL.md · Build the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without…
ramboz/jig · skills/independent-review/SKILL.md · Build the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without…
rizwanzafaris/product-manager-os · skills/runtime/independent-review/SKILL.md · Challenge product artifacts for unsupported claims and gate omissions. Use when an independent review must report…
