mcpField
G
graphify

graphify

github.com/howell5Development12.0k installsUpdated 11w ago
Repository

About graphify

graphify is an agent skill and CLI-based code navigation layer that builds a structural index of source files, symbols, and relationships. Developers and coding agents can query the index to locate code, then update it manually after edits.

Key features

  1. 01AST-based code structure indexing
  2. 02Case-insensitive symbol search
  3. 03Incremental and git-diff-based updates
  4. 04Support for 13 programming languages

Use cases

  1. 01Finding symbols in unfamiliar codebases
  2. 02Locating code before broad text searches
  3. 03Refreshing the index after code edits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/howell5/willhong-skills --skill graphify

After installing, type/graphifyin Claude Code to confirm it loaded.

Details

From the project README

graphify — Code Navigation Layer

Structural index of the codebase. Know what exists, where, and how it connects — before you grep.

Requires CLI: npm i -g graphify-ts (uses Bun runtime).

Manual updates only. The graph does not refresh on its own — you (or the user) run graphify update or graphify build when you want a fresh index. This avoids write conflicts in git worktrees and other multi-session setups.

First-time setup (one-time per machine)

npm i -g graphify-ts    # install CLI

Then, once per project:

graphify build .

After that, refresh manually whenever the index drifts from the code (see graphify update below).

Commands

/graphify build — Build index (first time, or full rebuild)
graphify build .

Scans all source files, extracts AST structure, saves to graphify-out/graph.json.

Report: "Indexed {files} files, {nodes} symbols, {edges} relationships"

/graphify query <name> — Search for symbols
graphify query graphify-out/graph.json <name>

Case-insensitive search. Returns matching symbols with file locations.

/graphify update <files...> — Incremental update after edits
graphify update graphify-out/graph.json <file1> [file2...]

Re-extract only the specified files. Run this after editing code if you plan to query the graph again in the same session.

/graphify auto-update — Bulk update from git diff
graphify auto-update [dir]

Computes changed code files via git diff + untracked files, then calls updateIndex. Silent when there's nothing to do. Convenient for refreshing after a batch of edits without naming each file.

When to Use

Before searching code: If graphify-out/graph.json exists, query it before Glob or Grep. The graph tells you which files contain which symbols. This is the main value — replace blind keyword search with structured lookup.

After editing: If you'll query the graph again in the same session, run graphify update <edited-files> (or graphify auto-update for a bulk refresh). Otherwise leave it — the next graphify build or update will catch up.

Exploring unfamiliar code: Run /graphify query <concept> to find entry points without guessing filenames.

Supported Languages

Python, JavaScript, TypeScript (JSX/TSX), Go, Rust, Java, C, C++, Ruby, C#, Kotlin, Scala, PHP

Graph Output

Saved as graphify-out/graph.json:

{
  "nodes": [{ "id": "main::app", "label": "App", "sourceFile": "main.py", "sourceLocation": "main.py:5" }],
  "edges": [{ "source": "file::main", "target": "main::app", "relation": "contains", "confidence": "EXTRACTED" }],
  "metadata": { "files": 10, "nodes": 45, "edges": 62 }
}

Edge relations: contains, method, imports, imports_from, calls (INFERRED), inherits

Comments

Markdown supported