LGTM

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 a developer enters lgtm mode, they stop critically reviewing code and start rubber-stamping everything with a thumbs-up. Maybe it's a Friday afternoon, maybe the PR queue is 40 deep, or maybe they just don't have the bandwidth to care — whatever the reason, every diff looks fine and every merge request gets waved through. It's the coding equivalent of nodding along without listening, and it's how bugs quietly sneak into production.

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.

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.

Let me know. Tacked onto the end of an offer, question or request to signal "no rush, but get back to me when you can". A workhorse of professional and casual messaging alike.