Fake busy check from today’s git history
A pile of sessions and nothing done: today’s merges told apart from busywork, then one sentence on tomorrow’s first task.
373 saves on X, as of Posted
Prompt
Don't summarize yet, and don't praise me. Ask me one question at a time, and wait for my answer before the next one.
1. First, look at today's commits, branches and uncommitted changes yourself. Pick out what actually got merged and what was just back-and-forth edits. Then ask me: Going only by these records, not by what I say, what would an outsider think I really want?
2. Then ask me: What am I avoiding with all this busywork?
3. Next, ask me: What's the most embarrassing reason I still haven't done that thing? I want the one that sounds weak, scared or lazy, not the one that sounds reasonable.
4. If my answers are vague, keep pushing until I get specific. Five questions max. At the end, give me just one sentence: what to do first tomorrow, and what counts as done.Next Send it to Claude Code or Codex in your project before you log off.
The biggest trap with coding agents is fake busy. You open a pile of sessions, grind past midnight, then look back and nothing actually got done.
Before you log off each day, have Claude Code or Codex check your git history.
Share this tip
