Ujjansh Sundram / Portfolio
SELECTED WORK / 02

GraphXploit

Understand a code change before following every reference by hand. A local workbench maps repository relationships and Git changes to potentially affected symbols.

MOTION STUDY / CONNECTION
01 / 03

Build the index

Source is indexed locally without executing the repository.

Illustration of the project workflow.

  1. Build the index

    Source is indexed locally without executing the repository.

  2. Follow a change

    Git changes connect to symbols and their static dependencies.

  3. Inspect the context

    Explore related code locally; AI is optional with a configured endpoint.

On the workbenchTrace a sample change

In the sample application, main calls authenticate, which calls log_login. A change to the helper puts both callers on the review list. Read the source

Tree-sitterSQLiteGitOptional AI

The problem

A small change can touch code far beyond the file being edited. That context is difficult to reconstruct in an unfamiliar repository.

The approach

Static indexing, dependency graphs, and Git impact tracing bring related symbols together. Incremental SQLite indexing avoids parsing unchanged files again.

The result

A local CLI and graph workbench. The Lite edition stays local; the AI edition uses an endpoint you configure. Static relationships do not guarantee runtime behavior.

Explore repository