LGTM meaning: LGTM stands for “looks good to me.” It is a short way to approve something, most often a code change in a pull request, but also a document, design or plan shared by email or chat. Writing LGTM tells the author you reviewed it and have no blocking concerns.
What does LGTM mean at work?
LGTM is a sign-off. In software teams, it has a specific job: a reviewer comments “LGTM” on a pull request or code review to say the change can move forward. Many teams require one or two LGTMs before code is merged.
Outside engineering, LGTM has spread to marketing, product, design and operations. Someone shares a draft and asks for a quick check. A reply of “LGTM” means “approved from my side.”
Because it’s short, LGTM can mean different levels of review. Sometimes it follows a careful check. Sometimes it’s a quick skim. If the stakes are high, it’s worth saying how closely you looked.
You may also see variants like “LGTM with nits” (approved, with tiny optional suggestions) or “LGTM once tests pass.”
Examples of LGTM in emails and messages
Code review comment: “LGTM. Nice cleanup of the error handling.”
Pull request: “LGTM with one nit: rename tmp to cachedResult. Fine to merge after.”
Slack: “Read the launch email draft, LGTM! Ship it.”
Email reply: “LGTM on the budget numbers. Looping in Finance for final sign-off.”
Design review: “Homepage mockup LGTM, assuming the copy is final.”
LGTM vs approved vs ACK
| Term | Meaning | Strength |
|---|---|---|
| LGTM | Looks good to me; I have no blocking concerns | Informal approval |
| Approved | Formal sign-off, often recorded in a tool | Official |
| ACK | Acknowledged; I saw this | Receipt only, not approval |
| Nit | A minor, optional suggestion | Not blocking |
In many code tools, the formal “Approve” button matters more than the LGTM comment. Check your team’s process.
How to use LGTM correctly
- Only say it if you actually reviewed it. LGTM can be treated as a real approval.
- Add context when it matters. “LGTM, I checked the logic but not the styling” sets the right expectations.
- Separate blocking from non-blocking comments. Use “nit” for optional suggestions.
- Use the formal approval when required. A chat LGTM may not count in your review tool.
- Write it out for clients and executives. “Looks good to me, approved” is clearer than an acronym they may not know.
When to avoid it: for legal, financial or safety sign-offs where a clear written approval is expected.
How do you give an LGTM in a pull request?
On most code platforms, typing “LGTM” in a comment is friendly, but it may not count as a formal approval. Tools such as GitHub and GitLab have a review button where you choose to approve the change. Many teams require at least one formal approval before code can be merged.
A common pattern is to do both: choose the approve option and leave a short note, such as “LGTM, nice cleanup on the error handling.” That way the tool records the approval and the author gets useful feedback.
Other code review acronyms you’ll see with LGTM
| Acronym | Stands for | What it means in a review |
|---|---|---|
| PTAL | Please take a look | The author is asking for a review, or a second look after changes |
| Nit | Nitpick | A small, optional suggestion that shouldn’t block approval |
| SGTM | Sounds good to me | Agreement with a plan or idea, often before any code is written |
| ACK | Acknowledged | “I’ve seen this,” which isn’t always the same as approval |
| WIP | Work in progress | Not ready for final review yet. See WIP |
When should you not say LGTM?
LGTM is a sign-off. It tells the author, and often the whole team, that you checked the work and are comfortable with it going ahead. Hold off when:
- You only skimmed it. Say “Skimmed it, looks fine at a glance, but someone should do a full review.”
- It’s outside your area. Say “Can’t judge the database part. Tagging Maria for that.”
- You have a real concern. Raise it first. Approving with an unresolved problem can let a bug reach customers.
- Tests are failing. Wait for them to pass, or approve with a clear note that it depends on the tests.
Outside engineering, the same rule applies to documents and plans. If your manager is counting on your LGTM before sending something to a client, make sure you’ve actually read it.
Is LGTM used outside software teams?
Yes. LGTM started in code review, but it has spread to any team that shares drafts in chat. Marketing teams use it to approve copy, designers use it on mockups, and managers use it to sign off on plans. The meaning is the same everywhere: “I’ve reviewed this and I’m fine with it going ahead.”
Marketing: “LGTM on the email copy. Schedule it for Tuesday.”
Finance: “Budget sheet LGTM. Sending to the VP now.”
If your workplace uses a formal approval step, like a sign-off in a project tool, treat LGTM in chat as a friendly note and still complete the official step.
Related terms
Browse more short forms in our Workplace Acronyms hub.
FAQ
What does LGTM stand for?
LGTM stands for looks good to me. It is a quick approval used in reviews.
What does LGTM mean in code review?
In code review, LGTM means the reviewer checked the change and has no blocking concerns, so it can move toward merging.
Is LGTM professional?
Yes, within teams that use it, especially in tech. For clients or formal approvals, write out your approval in full.
What does LGTM with nits mean?
It means the work is approved, and the reviewer has a few small, optional suggestions that don’t need to block it.
