introducing greptile's linear integration
@dakshgup19K followers
21,106 views
14 Comments
Comments from the original post on X (Twitter)

@dakshgup
read the docs:
5 likes

@swwvve
Cancelled my plan today
4 likes

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

@brianchew
yummy
1 like

@lflarota
@garrytan ouu maaannn, finallyyy! thank you thank you!
1 like

@makatack_
goat
1 like

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

@abhitwttt
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.

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

@KakaluoteW45042
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.

@buildwbhoomika
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.

@jonsegov
When's the click up integration coming?

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

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