Video wird geladen...
Video konnte nicht geladen werden
introducing greptile's linear integration greptile: - finds the linear issue associated with your PR (even if it isn't linked) - ensures that the PR fulfills the requirements of the issue. sometimes PRs aren't buggy, just incomplete. some of the best teams define "complete" in linear!
20,920 Aufrufe • vor 1 Monat •via X (Twitter)
14 Kommentare

read the docs:

Cancelled my plan today

At first I read it as reptile linear regression. That I would love to learn about!!!

yummy

@garrytan ouu maaannn, finallyyy! thank you thank you!

goat

Reviewing code without checking the issue is like proofreading an answer without reading the question. A clean PR can still solve the wrong problem.

A better tagline for greptile Condom for your Claude. Btw, genuinely love your product. We actually have a rule at our company, nothing gets merged until it gets a 5/5 from Greptile.

Could you share how teams are measuring “complete” after adopting this approach? Interested in any metrics you’ve observed.

This is exactly the failure mode I see with agent-generated PRs — they nail the happy path but silently skip edge cases mentioned in the issue. Automated completeness checking against the issue spec catches what code review misses.

A clean PR can still solve the wrong problem. Connecting code review to the Linear issue makes completeness part of the review, not an afterthought.

When's the click up integration coming?

code that works isn't always code that's complete. this is a really useful layer for agents

what's the usecase for greptile over codex/cc? is it just pricing

