GraphDev

Why It Won — our reading

The winning move looks like scope. Instead of another code assistant, it answers the one question every developer already asks: what breaks if I change this. Grounding that in a dependency graph rather than pure model inference gives the team a structural story about why it holds up as a codebase grows, which is easy to defend in front of a panel. And on GitLab's home turf of repositories, making code itself the subject sat naturally with the hosts.