SCRIPT CHECK · 60 SECONDS
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.
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “Every security issue makes me look like I'm not thorough”, including the private rule underneath it: If a security finding appears under my name, it means I wasn't careful enough to prevent it, no matter who wrote the flagged line or when the vulnerability was actually disclosed.
QUIET
“Every security issue makes me look like I'm not thorough” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “A finding is information about the codebase, not a grade on how carefully I work.”
PRESENT
“Every security issue makes me look like I'm not thorough” wins some small decisions before you catch it. Your useful interruption is: “I can trace where a flaw came from without turning that trace into a verdict on me.”
ACTIVE
“Every security issue makes me look like I'm not thorough” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Open your last five security findings and privately note, for each one, whether it predates your ownership or came from your own recent change.
DOMINANT
Right now, “Every security issue makes me look like I'm not thorough” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Open your last five security findings and privately note, for each one, whether it predates your ownership or came from your own recent change.