Built on Relate — the embedded graph database by Neo4j

Know what else changes before your agent opens the PR.

Ripple turns a repository's git history into a Relate graph of commits, files and people. Coding agents ask it what usually changes together, who knows a file, and which coupled files are missing from a change — in one local command, no server.

Open the explorerpip install from GitHub →
$ ripple ingest .
ingested 3817 commits, 561 files, 857 authors, 3836 co-change edges into .ripple.rl in 1.26s
$ ripple check src/flask/json/provider.py src/flask/app.py
  ? src/flask/blueprints.py  — changed with src/flask/json/provider.py in 50% of its commits (6×)
  ? src/flask/helpers.py  — changed with src/flask/json/provider.py in 50% of its commits (6×)
  ? CHANGES.rst  — changed with src/flask/json/provider.py in 50% of its commits (6×)

Explore a real repository

Every number below comes from the full git history of pallets/flask, loaded into a Relate store with ripple ingest and exported with ripple export. Pick a file to see its context, or tick several to check a change set.

Node size = commits · edge = changed together ≥3×

How it works

One graph file, three kinds of nodes, and relationships an agent can traverse in-process.

1 · Ingest

git log --numstat becomes (:Commit)-[:TOUCHED]->(:File) and (:Commit)-[:AUTHORED_BY]->(:Author), written with batched Cypher UNWIND … MERGE into a single .ripple.rl store.

2 · Relate

A Cypher pass materialises [:CO_CHANGES {n, conf_ab, conf_ba}] between files, with directional confidence: how often B changed when A did. Bulk commits (>40 files) are skipped as noise.

3 · Ask

context, check and hotspots are graph traversals. Output is plain text for people and --json for agents, and check --strict works as a pre-commit hook or CI gate.

Made for coding agents

Drop the bundled skill into Claude Code, Cursor or Codex and the agent calls Ripple before editing and before committing. Because the store is a single file, every agent on the machine shares the same context.

# before editing
$ ripple --json context src/flask/sessions.py -k 3
{"path":"src/flask/sessions.py","changes":33,
 "co_changes":[{"path":"CHANGES.rst","together":19,"confidence":0.576},
   {"path":"src/flask/app.py","together":16,"confidence":0.485}, …],
 "experts":[{"author":"David Lord","commits":26}, …]}
# before committing (.git/hooks/pre-commit)
ripple check --staged --strict || {
  echo "Ripple: coupled files missing — review above"; exit 1; }
# or query the graph directly
$ relate -d .ripple.rl "MATCH (f:File)-[r:CO_CHANGES]-(o) RETURN …"