This is the part where you'd normally pull the junior engineer aside and politely give them a stern talking to until they understood what they did wrong.
If anybody has suggestions for how to do this with LLMs (short of maintaining CLAUDE_wall_of_shame.md), please share.
Edit: for the record, yes I do run a linter, and generally try not to impose bikeshedding or soapboxes on my peers. It's just that there are certain patterns that I personally am not going to commit under my own username as the engineer of record.
Edit 2: I saw another comment recommending "Always confirm with me before doing $x" (and then always denying). Seems like it might work.
What I do to avoid this is to manually approve each change Claude is doing
I think the yolo mode of auto approve changes is to the root cause, which is probably a little embarrassing to be that engineer we’re all collectively pulling aside to ask:
Is this the result of automatically letting the robot tune your machine?
“Sync with the server periodically to get the latest”
Tracks for what we can infer