When this happens, how much does it change what you do next: You reread `git log` more than the actual diff, checking whether the story of your mistakes is still reconstructable.

It does not change my next move

SCRIPT CHECK · 60 SECONDS

“Force-pushing a fix feels like hiding the evidence”

See what this thought is changing.

Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.

5 questions · about 1 minute · no account needed

What this self-check measures

This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “Force-pushing a fix feels like hiding the evidence”, including the private rule underneath it: If anyone can see the commit where I got it wrong before I got it right, they'll treat that as proof I don't actually know what I'm doing, so the history has to look clean from the very first line.

See all result bands

QUIET

Quiet signal

“Force-pushing a fix feels like hiding the evidence” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “My commit history is a workspace, not a confession I need to redact.”

PRESENT

Present in the background

“Force-pushing a fix feels like hiding the evidence” wins some small decisions before you catch it. Your useful interruption is: “A rough first attempt is proof I iterate, not proof I'm unqualified.”

ACTIVE

Active pattern

“Force-pushing a fix feels like hiding the evidence” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: In a throwaway local git repo, commit a deliberately messy first attempt, then commit the real fix on top without squashing or force-pushing, and reread the log once.

DOMINANT

Getting the final word

Right now, “Force-pushing a fix feels like hiding the evidence” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: In a throwaway local git repo, commit a deliberately messy first attempt, then commit the real fix on top without squashing or force-pushing, and reread the log once.