Skip to main content
The assistant skill produces a visualization, report, and graph under graphify-out/. Headless code-only extraction writes the graph and analysis first. Run graphify cluster-only . --no-label to generate the report and visualization without model-generated labels. Use graphify export html to regenerate the visualization separately.

​
Graph representation

The JSON uses NetworkX node-link conventions. Nodes carry identifiers and labels, and usually source information such as source_file and file_type. Edges connect node IDs and carry relationship and confidence metadata. Fields vary by extractor and release; consume only fields your workflow needs. Current readers support graphs with a links array and compatibility inputs with an edges array. Group relationships can appear as graph metadata. Do not assume every node corresponds to a function or that every edge has a line number.

​
Move or share a graph

You can point a query at a specific file:
The graph contains labels and source-derived context. Treat it with the same access controls as the source repository. See team workflows before committing generated artifacts.

​
Change the output location

GRAPHIFY_OUT changes the output directory. Use a distinct directory when multiple worktrees need their own graph. See configuration.

​
Next steps

Try it in Graphify

We build and host the graph for you. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Supported inputs

Languages and documents Graphify can read.

Export and reuse your graph

Turn the graph into HTML, JSON, and more.