built for Hacktoberfest · sponsor track: Graphify

OneGraph

Graphify builds the real structural dependency graph: tree-sitter, $0 LLM cost. Gemma 4 narrates it, with citations that trace back to a real file:line, not a guess.

Live PR demo Open the interactive graph

How it works

Two pipelines, one real graph

Build the graph

  1. repo
  3. graphify extract, tree-sitter AST, $0 LLM
  5. graphify label, names every community
  7. exported, deployed to Vercel

Review a pull request

  1. PR diff
  3. graphify affected, real blast radius
  5. Gemma 4 writes the plain-English review
  7. posted as a PR-Agent comment, with graph link

Graphify extracts

tree-sitter AST over the real repo: every call, import and containment edge, $0 LLM cost to build.

Gemma 4 narrates

reads the real graph traversal, writes the plain-English review, and cites only modules that actually exist.

Wired into PR-Agent

comment /graph_risk on any PR: it posts the risk review and a link to the full live graph.

Real scale, not a toy demo

Four real repos, mapped end to end

Every node and edge below is a real extracted symbol. Graphify ran on the actual public repo, nothing trimmed, nothing simulated.

0
total nodes mapped
0
total edges mapped
$0
graph build cost

pallets / flask

web framework

0
nodes
0
edges

NVIDIA / Megatron-LM

LLM training framework

0
nodes
0
edges

Graphify-Labs / graphify

the sponsor tool, graphing itself

0
nodes
0
edges

supabase / supabase

Postgres dev platform

0
nodes
0
edges

Not just syntax-checked

Live in a real pull request

Verified end to end against a real demo PR, through the GitHub API, not just a clean exit code. Open the PR →

The posted /graph_risk review: Risk High, a downstream-dependents table, and a plain-English analysis

The structured review comment: risk level computed from a real blast-radius count, a per-file table, and the analysis paragraph Gemma 4 writes.

An inline review comment anchored to the exact changed line, listing real downstream dependents

An inline comment anchored to the exact diff line, greptile/CodeRabbit-style, from the same blast-radius traversal.

Two tools, two real diffs

Pluggable, not rebuilt

qodo-ai/pr-agent

Two lines in command2class register the new /graph_risk command. Live-verified above.

AsyncFuncAI/deepwiki-open

One env var gates research_chat()'s context source. Unset, the original embedding-RAG path is untouched.

Why this exists

A code review that says a change "looks risky" without showing why is a guess. A dependency diagram made of hand-drawn boxes and arrows is also a guess. OneGraph removes both guesses: Graphify extracts the graph once, cheaply and deterministically; Gemma 4 only ever talks about nodes and edges that are actually there.