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.