REALITYWIPE

OLD SCRIPT DETECTED

I rehearse my defense before the comments even arrive

Try this response:

I can answer a real comment when it exists. I don't owe one to a comment that hasn't been written.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

I rehearse my defense before the comments even arrive

YOUR RECORDED RESPONSE

I can answer a real comment when it exists. I don't owe one to a comment that hasn't been written.

ONE PRIVATE MOVE

Once you push the branch, write your one genuine open question about the diff in a private note and stop — no rehearsed answers to comments that don't exist yet.

The Opening Statement for a Trial That Hasn't Started

SCENE_01

Nine Fourteen, Zero Comments

You push the branch at 9:14 and the PR sits there with a green check and no reviewer's name on it yet. Nobody has clicked into the diff. Still, you're already narrating: 'I used a map here because the list stays under twenty items, and I chose the early return because—' You're defending line twelve to a courtroom that doesn't exist yet, minutes before anyone could plausibly have opened the tab.

SCENE_02

Building the Case File Nobody Ordered

The private math: if you don't have an answer ready, the reviewer will conclude you didn't think it through, and that verdict will outlast any two-line fix. So you hold the 'ready for review' click a little longer, cross-examining your own choices, drafting replies to objections nobody has raised. You end up with a full defense brief for a hearing that, so far, is a blank comment thread.

SCENE_03

The Docket Is One Line, Not a Trial

A more accurate read: someone opening your diff is checking whether the code does what it says, not building a prosecution against you. Most comments turn out to be a single clarifying line, not a summation. Try this instead: once the branch is pushed, write your one genuine open question in a private note and stop there, instead of drafting rebuttals to questions no one has asked yet.

TRACE · 01/04

How this script runs you

  • You delay clicking 'ready for review' to finish mentally answering questions nobody has typed yet.
  • You draft and re-phrase replies to comments in your head before a single comment exists.
  • Walking away from the keyboard, you keep narrating justifications for lines a reviewer may never open.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Review Trial

The rule underneath this thought: if I don't have a ready answer prepared before anyone asks, that gap itself will be read as proof I didn't know what I was doing — so the defense has to be finished before the trial opens, not during it.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • I can answer a real comment when it exists. I don't owe one to a comment that hasn't been written.
  • A reviewer reading code is not a jury reading a verdict against me.
  • My open question goes in a note, not into a rehearsed defense for an empty thread.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

I rehearse my defense before the comments even arrive

I say

I can answer a real comment when it exists. I don't owe one to a comment that hasn't been written.

Then I do one thing

Once you push the branch, write your one genuine open question about the diff in a private note and stop — no rehearsed answers to comments that don't exist yet.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "I rehearse my defense before the comments even arrive". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

Why do I keep holding the 'ready for review' button while I finish justifying lines no one has flagged?

Because the private rule says the defense must be complete before anyone can ask a question, so the button waits until every line has a ready answer — even though most lines will never be asked about at all.

Is rehearsing my answers before a comment lands actually useful preparation?

Occasionally one line does need a clear explanation, but rehearsing responses to comments that don't exist yet mostly just extends the wait before you press submit, without changing what a reviewer will actually ask.

What's different about defending a line versus just explaining a choice?

Explaining a choice happens once, when someone asks. Defending a line happens in your head repeatedly, before, during, and after review, whether or not the question ever comes — that repetition is the tell, not the content of what you'd say.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script