Verified:GitHub

graphify

Extract a navigable knowledge graph from project folders into HTML, JSON, and audit report.

Updated Mar 25, 2026

Search Tags:#documentation #code-analysis #knowledge-graph #audit-trail #graph-visualization #graphify #project-introspection

Ready to run

npx skills add https://github.com/SOLEROM/cldlab --skill graphify-solerom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/SOLEROM/cldlab/tree/main/grif
Command: npx skills add https://github.com/SOLEROM/cldlab --skill graphify-solerom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Graphify enables teams to convert a folder of code, docs, and papers into a navigable knowledge graph that reveals structure, relationships, and dependencies, with persistent outputs for auditing.

Core Features & Use Cases

Persistent graph: stores relationships in graphify-out/graph.json for session-to-session continuity.
Honest audit trail: edges are EXTRACTED or INFERRED to show what was found vs inferred.
Visual and machine-readable outputs: HTML visualization, GraphML/JSON, and an audit report.
Use case: Understand a codebase, map research materials to concepts, or plan refactors and onboarding.

Quick Start

Run graphify on a project folder to generate an interactive graph and outputs in graphify-out.

Frequently Asked Questions about graphify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a knowledge graph from a codebase to visualize project structure?▼

To generate a knowledge graph from a codebase, you run graphify on your project folder containing code, docs, and papers. It extracts an interactive HTML visualization and a machine-readable graph JSON to reveal structural relationships.

What is an audit trail in code analysis and how does it show inferred dependencies?▼

An audit trail in code analysis tracks whether relationships are explicitly extracted from files or inferred by the tool. Graphify produces a GRAPH_REPORT.md that distinguishes found dependencies from inferred ones for honest auditing.

Can I build a navigable knowledge graph from research papers and documentation in a repository?▼

Yes, you can build a navigable knowledge graph from research repositories and personal codebases. Graphify maps research materials and documentation to concepts, outputting a persistent graph JSON for session-to-session continuity.

How do I extract a machine-readable graph JSON from a software project for refactoring?▼

You can extract a machine-readable graph JSON by running graphify on your software project folder. It generates graphify-out/graph.json, which stores structural dependencies to help you plan refactors and onboarding.

Does graphify require any external dependencies or components to map code relationships?▼

No, graphify requires no external dependencies or components to map code relationships. You simply run it on your project folder to produce the HTML visualization, graph JSON, and audit report outputs.

What are the limitations of using automated code analysis for project introspection?▼

Automated code analysis for project introspection relies on inferred edges when explicit relationships are absent, which may introduce assumptions. Graphify mitigates this by providing an audit report that clearly separates extracted data from inferred connections.