lgtm mode

An lgtm fail is what happens when someone approves a pull request without actually reading it and the code later breaks production. The phrase captures both the action — the lazy rubber-stamp — and the consequence: a bug, an outage, or a security hole that traces back directly to a drive-by approval. It's the ultimate dev accountability moment, immortalized in post-mortems and passive-aggressive Slack threads alike.

"Looks Good To Me." Shorthand approval on a pull request or code review, signaling the reviewer has no blocking concerns. Can be left solo or stacked with emojis — "LGTM 🚀" for ship-it energy.

A sus lgtm is an approval that raises more questions than it answers — when someone says 'looks good to me' on code that clearly hasn't been properly reviewed, or gives the green light a suspicious amount faster than anyone should. The sus qualifier signals that the review itself smells off: maybe they're covering for bad work, maybe they didn't look at all, maybe they merged their own PR. Something is definitely not right here.

When something is low key lgtm, you're grudgingly admitting it's pretty solid without wanting to make a big deal about it. The 'low key' does all the work — you're not gushing, you're not stamping it approved with fanfare, you're just quietly acknowledging that yeah, this works, this slaps, this is actually fine. It applies to code, to food, to a song you didn't expect to like. The restrained approval is the whole point.

A behavioral state in which someone seems locked into taking Ls — every choice leads to a worse outcome, every plan collapses, every social read is wrong. When you're in L mode, you're not just having bad luck; you're actively contributing to your own loss streak through a series of questionable decisions that look obvious in hindsight. Friends can see you're in L mode before you do. The mode implies a temporary condition — you can exit L mode — but while you're in it, everything you touch turns into a highlight reel of failure.