正在加载视频...

视频加载失败

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 次观看 • 1 个月前 •via X (Twitter)

14 条评论

Daksh Gupta 的头像
Daksh Gupta1 个月前

read the docs:

cyrus 的头像
cyrus1 个月前

Cancelled my plan today

Alex 的头像
Alex1 个月前

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

Brian Chew 的头像
Brian Chew1 个月前

yummy

luis 的头像
luis1 个月前

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

John Wei 的头像
John Wei1 个月前

goat

KP bhoomika 的头像
KP bhoomika1 个月前

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

Abhi 的头像
Abhi1 个月前

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.

Edgex 的头像
Edgex1 个月前

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

琦玉老师 的头像
琦玉老师1 个月前

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.

KP bhoomika 的头像
KP bhoomika1 个月前

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.

segov 的头像
segov1 个月前

When's the click up integration coming?

Sridhar A 的头像
Sridhar A1 个月前

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

arun 的头像
arun1 个月前

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

相关视频