← back

SemaDiff: Identifying Semantic-Changing Commits with Generated Code and Tests

Distinguishing semantic-preserving commits from changing ones remains an open challenge in software repository mining. While existing approaches detect refactoring commits accurately, they cannot ensure that a commit is purely semantic-pres

https://arxiv.org/abs/2607.13111v1 ↗
Thesis fit
Good fit

Within your typical scope; diligence still required.

Edit thesis
In your usual scope
Idea match None

How close the company’s idea is to your thesis statement

Sector ai

Overlap with sectors you care about

Geography Unknown

Location unknown — scores 0

Your thesis: “We back exceptional technical founders building AI-first products and infrastructure, deploying $100K checks within 24 hours.”

Founder → stable Traction → stable Idea vs market → stable
Generate memo
Add / edit details

Correct facts used on the next screening or memo.

Similar baseline plays (YC · idea space)

FifthTry · Active
Continuous Documentation To End Documentation Rot
founders not scraped yet
Redspread · Acquired
Version control for software environments
Openbase · Inactive
Open-source library discovery
founders not scraped yet
Kivo · Inactive
Git for Documents
founders not scraped yet
Waydev AI · Active
Track AI-generated code from commit to production
founders not scraped yet