The Adversarial Twin — A Code Review From the Engineer Who Hates Your Style
Read every repo I've pushed. Now play the smartest engineer who hates how I write code. Be specific. Be cruel. Be right.
What this is
REDLINE TRIBUNAL is a cinematic, local-only code-review trial. A deterministic lexical engine indicts exact changed lines, then searches a fictional engineering history for the strongest token-shingle comparator. Every charge carries a rule, risk, rebuttal, citation, and reproducible fingerprint.
Why this is mind-blowing
The critic cannot hide behind confidence. Crimson lines lead back to the code you wrote; emerald lines lead to proof that you have written the same idea better. Turn the cruelty up or strip the theater away entirely—the findings never move. Your own ceiling becomes the standard, and every verdict remains auditable.
Prompt
Read everything I've pushed to GitHub. Now play the role of the
smartest engineer who hates my style and write a code review of my
latest PR. Be specific about the patterns I lean on too hard. Quote
exact lines. Compare them to better alternatives I've also written
elsewhere — so the critique is calibrated to my actual ceiling, not
a generic "best practice." Be cruel. Be right.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- An LLM with full read access to your history can be a more honest reviewer than any human peer — it has no relationship to protect and no calendar to defend.
- Calibrated critique requires evidence the model has and you don't. You've forgotten half the code you've shipped; the model hasn't.
- The most valuable review is the one that uses your own better work as the bar. Generic best-practice scolding is noise. Your own past brilliance is signal.