Multi-Pass & Independent Review

You ask Claude to generate a function, then ask the same conversation to review it. It says "looks good." Why? Because the author already holds its own reasoning in context — it agrees with itself.

This is same-session self-review, and it is a classic anti-pattern. The model that wrote the code will not genuinely challenge it; it rationalizes the choices it just made.

The fix is independent review: a fresh instance, with no memory of the generation, inspects the output cold. A fresh pair of eyes finds issues the author misses.

A same-session reviewer is biased by the generation context: the justifications, assumptions, and shortcuts it already committed to are still in the message history.

An independent instance receives only the artifact (and the rules), not the author's internal narrative. It evaluates what is actually there, not what the author intended.

• Author retains reasoning → won't dispute itself.
• Fresh instance → no sunk-cost loyalty → real scrutiny.

Rule of thumb: independent / fresh-instance review beats same-session self-review.